Displaying 10 results from an estimated 10 matches for "ioeventfd_in_range".
2015 Mar 11
2
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...vmppc_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 big endian (TARGET_WORDS_BIGENDIAN) by
default.
This patch adds an extra swap in v...
2015 Mar 11
2
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...vmppc_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 big endian (TARGET_WORDS_BIGENDIAN) by
default.
This patch adds an extra swap in v...
2015 Mar 11
4
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
..._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 big endian (TARGET_WORDS_BIGENDIAN) by
>...
2015 Mar 11
4
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
..._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 big endian (TARGET_WORDS_BIGENDIAN) by
>...
2015 Mar 11
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...> |
> +-> __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 big endian (TARGET_WORDS_BIGENDIAN) by
> default.
>
>...
2015 Mar 11
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...> |
> +-> __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 big endian (TARGET_WORDS_BIGENDIAN) by
> default.
>
>...
2015 Mar 12
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...gt; > > 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 big endian (TARGET_WORD...
2015 Mar 12
0
[PATCH] virtio-pci: fix host notifiers on bi-endian architectures
...gt; > > 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 big endian (TARGET_WORD...
2013 Apr 04
1
[PATCH RFC] kvm: add PV MMIO EVENTFD
...93e5b05..1b7619e 100644
--- a/virt/kvm/eventfd.c
+++ b/virt/kvm/eventfd.c
@@ -579,6 +579,7 @@ struct _ioeventfd {
struct kvm_io_device dev;
u8 bus_idx;
bool wildcard;
+ bool pvmmio;
};
static inline struct _ioeventfd *
@@ -600,7 +601,15 @@ ioeventfd_in_range(struct _ioeventfd *p, gpa_t addr, int len, const void *val)
{
u64 _val;
- if (!(addr == p->addr && len == p->length))
+ if (addr != p->addr)
+ /* address must be precise for a hit */
+ return false;
+
+ if (p->pvmmio)
+ /* pvmmio only looks at the address, so always a hi...
2013 Apr 04
1
[PATCH RFC] kvm: add PV MMIO EVENTFD
...93e5b05..1b7619e 100644
--- a/virt/kvm/eventfd.c
+++ b/virt/kvm/eventfd.c
@@ -579,6 +579,7 @@ struct _ioeventfd {
struct kvm_io_device dev;
u8 bus_idx;
bool wildcard;
+ bool pvmmio;
};
static inline struct _ioeventfd *
@@ -600,7 +601,15 @@ ioeventfd_in_range(struct _ioeventfd *p, gpa_t addr, int len, const void *val)
{
u64 _val;
- if (!(addr == p->addr && len == p->length))
+ if (addr != p->addr)
+ /* address must be precise for a hit */
+ return false;
+
+ if (p->pvmmio)
+ /* pvmmio only looks at the address, so always a hi...