Displaying 8 results from an estimated 8 matches for "kvm_iodevice_write".
2015 Mar 11
2
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...O store emulation
in KVM. Debugging shows that:
kvmppc_emulate_mmio()
|
+-> kvmppc_handle_store()
|
+-> kvm_io_bus_write()
|
+-> __kvm_io_bus_write() returns -EOPNOTSUPP
This happens because no matching device was found:
__kvm_io_bus_write()
|
+->kvm_iodevice_write()
|
+->ioeventfd_write()
|
+->ioeventfd_in_range() returns false for all registered vrings
Extra debugging shows that the TX vring number (16-bit) is supposed to
be 0x0100 but QEMU passes 0x0001 to KVM... This happens *again* because
QEMU still assumes powerpc is...
2015 Mar 11
2
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...O store emulation
in KVM. Debugging shows that:
kvmppc_emulate_mmio()
|
+-> kvmppc_handle_store()
|
+-> kvm_io_bus_write()
|
+-> __kvm_io_bus_write() returns -EOPNOTSUPP
This happens because no matching device was found:
__kvm_io_bus_write()
|
+->kvm_iodevice_write()
|
+->ioeventfd_write()
|
+->ioeventfd_in_range() returns false for all registered vrings
Extra debugging shows that the TX vring number (16-bit) is supposed to
be 0x0100 but QEMU passes 0x0001 to KVM... This happens *again* because
QEMU still assumes powerpc is...
2015 Mar 11
4
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...e()
> > |
> > +-> kvm_io_bus_write()
> > |
> > +-> __kvm_io_bus_write() returns -EOPNOTSUPP
> >
> > This happens because no matching device was found:
> >
> > __kvm_io_bus_write()
> > |
> > +->kvm_iodevice_write()
> > |
> > +->ioeventfd_write()
> > |
> > +->ioeventfd_in_range() returns false for all registered vrings
> >
> > Extra debugging shows that the TX vring number (16-bit) is supposed to
> > be 0x0100 but QEMU passes 0x0001...
2015 Mar 11
4
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...e()
> > |
> > +-> kvm_io_bus_write()
> > |
> > +-> __kvm_io_bus_write() returns -EOPNOTSUPP
> >
> > This happens because no matching device was found:
> >
> > __kvm_io_bus_write()
> > |
> > +->kvm_iodevice_write()
> > |
> > +->ioeventfd_write()
> > |
> > +->ioeventfd_in_range() returns false for all registered vrings
> >
> > Extra debugging shows that the TX vring number (16-bit) is supposed to
> > be 0x0100 but QEMU passes 0x0001...
2015 Mar 11
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...ate_mmio()
> |
> +-> kvmppc_handle_store()
> |
> +-> kvm_io_bus_write()
> |
> +-> __kvm_io_bus_write() returns -EOPNOTSUPP
>
> This happens because no matching device was found:
>
> __kvm_io_bus_write()
> |
> +->kvm_iodevice_write()
> |
> +->ioeventfd_write()
> |
> +->ioeventfd_in_range() returns false for all registered vrings
>
> Extra debugging shows that the TX vring number (16-bit) is supposed to
> be 0x0100 but QEMU passes 0x0001 to KVM... This happens *again* bec...
2015 Mar 11
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...ate_mmio()
> |
> +-> kvmppc_handle_store()
> |
> +-> kvm_io_bus_write()
> |
> +-> __kvm_io_bus_write() returns -EOPNOTSUPP
>
> This happens because no matching device was found:
>
> __kvm_io_bus_write()
> |
> +->kvm_iodevice_write()
> |
> +->ioeventfd_write()
> |
> +->ioeventfd_in_range() returns false for all registered vrings
>
> Extra debugging shows that the TX vring number (16-bit) is supposed to
> be 0x0100 but QEMU passes 0x0001 to KVM... This happens *again* bec...
2015 Mar 12
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...> kvm_io_bus_write()
> > > |
> > > +-> __kvm_io_bus_write() returns -EOPNOTSUPP
> > >
> > > This happens because no matching device was found:
> > >
> > > __kvm_io_bus_write()
> > > |
> > > +->kvm_iodevice_write()
> > > |
> > > +->ioeventfd_write()
> > > |
> > > +->ioeventfd_in_range() returns false for all registered vrings
> > >
> > > Extra debugging shows that the TX vring number (16-bit) is supposed to
> > &g...
2015 Mar 12
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...> kvm_io_bus_write()
> > > |
> > > +-> __kvm_io_bus_write() returns -EOPNOTSUPP
> > >
> > > This happens because no matching device was found:
> > >
> > > __kvm_io_bus_write()
> > > |
> > > +->kvm_iodevice_write()
> > > |
> > > +->ioeventfd_write()
> > > |
> > > +->ioeventfd_in_range() returns false for all registered vrings
> > >
> > > Extra debugging shows that the TX vring number (16-bit) is supposed to
> > &g...