search for: mmio

https://bugs.freedesktop.org/show_bug.cgi?id=67255 Priority: medium Bug ID: 67255 Assignee: nouveau at lists.freedesktop.org Summary: black screen after resuming from Hibernate QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: michele.cane at

Fixes "No Signal" via HDMI from NVIDIA Corporation ION VGA (rev b1) Ref. "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a The last working Fedora kernel 4.8.0-0.rc0.git3.1.fc25 Patched and tested with: $ modinfo -n nouveau

...9;get_results_from_database' in Module 'frmResults' in project DAO.Field The addition of dcom98, comctl32, comctl32.ocx result in the program crashing without the previous error message, at the point it attempts to verify a pass. Here is the terminal output: Code: ng\\Test\\" err:mmio:MMIO_ParseExtA No . in szFileName: "???3??????????@" err:mmio:MMIO_ParseExtA No . in szFileName: "???3??????????@" err:mmio:MMIO_ParseExtA No . in szFileName: "" err:mmio:MMIO_ParseExtA No . in szFileName: "C:\\Program Files\\xxxx\\Test\\" err:mmio:MMIO_Parse...

Hi, any one help? I have puzzled by the question of device''s MMIO areas. I know a MMIO operation of guest os handled by VMM as follow steps: 1: Qemu-dm does its initialization and presents virtual devices for guest os. 2: virtual bios executes PCI_setup, it will scan the pci bus and get configure space of all devices,then virtual bios allocation system resource...

These patches add a test device, useful to measure speed of MMIO versus PIO, in different configurations. As I didn't want to reserve a hardcoded range of memory, I added pci device for this instead. Used together with the kvm unittest patches I posted on kvm mailing list. To use, simply add the device on the pci bus. Example test output: vmcall 1519...

These patches add a test device, useful to measure speed of MMIO versus PIO, in different configurations. As I didn't want to reserve a hardcoded range of memory, I added pci device for this instead. Used together with the kvm unittest patches I posted on kvm mailing list. To use, simply add the device on the pci bus. Example test output: vmcall 1519...

When building with Clang + -Wtautological-compare and CONFIG_CPUMASK_OFFSTACK unset: arch/x86/mm/mmio-mod.c:375:6: warning: comparison of array 'downed_cpus' equal to a null pointer is always false [-Wtautological-pointer-compare] if (downed_cpus == NULL && ^~~~~~~~~~~ ~~~~ arch/x86/mm/mmio-mod.c:405:6: warning: comparison of array 'downed_cpus' equal...

Hi, this is continuation for the MMIO accessor rewrite and cleanup. I am currently running nv28 with these patches applied, but I cannot test on PPC. Please, review and comment. If the direction is good, I'll do the same to INSTANCE_{RD,WR} as I did for nv_{rd,wr}32, and change PRAMIN from drm_local_map to simple ioremap. Can the...

...in told me in the irc i should fill up a bugreport. System: Clean install of debian testing from 1.1.2016 dailybuild with kde chosen. Kernel 4.4.0-rc6 installed from experimental. The main needed information is this kernel panic captured with netconsole: [ 1059.265197] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b020 [ 1059.265516] nouveau 0000:00:0d.0: bus: MMIO write of 010d0001 FAULT at 00b010 [ 1060.724984] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b010 [ 1060.847845] nouveau 0000:00:0d.0: bus: MMIO write of 010a0001 FAULT at 00b010 [ 1060.848340] nouveau...

https://bugs.freedesktop.org/show_bug.cgi?id=82835 Priority: medium Bug ID: 82835 Assignee: nouveau at lists.freedesktop.org Summary: GeForce 8800 GS VDPAU h264 decoding hang QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: randrik at mail.ru

...redhat.com> wrote: > On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote: >> >> Why do we drop the previous way using "QEMUXXXX"? Something I missed? > > So that guests that bind to this interface will work fine with non QEMU > implementations of virtio-mmio. I don't understand this sentence. If there are pre-existing non-QEMU virtio-mmio implementations, then they're using LNRO0005, and we should use it too. If there are going to be implementations of virtio-mmio in future, then they will use whatever identifier we pick here. Either way, we g...

...redhat.com> wrote: > On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote: >> >> Why do we drop the previous way using "QEMUXXXX"? Something I missed? > > So that guests that bind to this interface will work fine with non QEMU > implementations of virtio-mmio. I don't understand this sentence. If there are pre-existing non-QEMU virtio-mmio implementations, then they're using LNRO0005, and we should use it too. If there are going to be implementations of virtio-mmio in future, then they will use whatever identifier we pick here. Either way, we g...

...ly virtio-pci is specified so that configuration of the device is done through a PCI IO space (via BAR 0 of the virtual PCI device). However, Linux guests happen to use ioread/iowrite/iomap primitives for access, and these work uniformly across memory/io BARs. While PCI IO accesses are faster than MMIO on x86 kvm, MMIO might be helpful on other systems which don't implement PIO or where PIO is slower than MMIO. Add a property to make it possible to tweak the BAR type. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> This is harmless by default but causes segfaults in memory.c wh...

...ly virtio-pci is specified so that configuration of the device is done through a PCI IO space (via BAR 0 of the virtual PCI device). However, Linux guests happen to use ioread/iowrite/iomap primitives for access, and these work uniformly across memory/io BARs. While PCI IO accesses are faster than MMIO on x86 kvm, MMIO might be helpful on other systems which don't implement PIO or where PIO is slower than MMIO. Add a property to make it possible to tweak the BAR type. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> This is harmless by default but causes segfaults in memory.c wh...

The nature of a virtio-mmio node is discovered by the virtio driver at probe time. However the DMA relation between devices must be described statically. When a virtio-mmio node is a virtio-iommu device, it needs an "#iommu-cells" property as specified by bindings/iommu/iommu.txt. Otherwise, the virtio-mmio device...

...23 PM, Li Liu wrote: > > > On 2014/10/27 17:37, Peter Maydell wrote: >> On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: >>> To get the interrupt reason to support such VIRTIO_NET_F_STATUS >>> features I add a new register offset VIRTIO_MMIO_ISRMEM which >>> will help to establish a shared memory region between qemu and >>> virtio-mmio device. Then the interrupt reason can be accessed by >>> guest driver through this region. At the same time, the virtio-mmio >>> dirver check this region to see irqfd...

...23 PM, Li Liu wrote: > > > On 2014/10/27 17:37, Peter Maydell wrote: >> On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: >>> To get the interrupt reason to support such VIRTIO_NET_F_STATUS >>> features I add a new register offset VIRTIO_MMIO_ISRMEM which >>> will help to establish a shared memory region between qemu and >>> virtio-mmio device. Then the interrupt reason can be accessed by >>> guest driver through this region. At the same time, the virtio-mmio >>> dirver check this region to see irqfd...

https://bugs.freedesktop.org/show_bug.cgi?id=111392 Bug ID: 111392 Summary: [NV110] bus: MMIO read of 00000000 FAULT at 619444 [ IBUS ] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau...

On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: > To get the interrupt reason to support such VIRTIO_NET_F_STATUS > features I add a new register offset VIRTIO_MMIO_ISRMEM which > will help to establish a shared memory region between qemu and > virtio-mmio device. Then the interrupt reason can be accessed by > guest driver through this region. At the same time, the virtio-mmio > dirver check this region to see irqfd is supported or not during >...

On 25 October 2014 09:24, john.liuli <john.liuli at huawei.com> wrote: > To get the interrupt reason to support such VIRTIO_NET_F_STATUS > features I add a new register offset VIRTIO_MMIO_ISRMEM which > will help to establish a shared memory region between qemu and > virtio-mmio device. Then the interrupt reason can be accessed by > guest driver through this region. At the same time, the virtio-mmio > dirver check this region to see irqfd is supported or not during >...