[Qemu-devel] [PATCH] Memory-API: Make eventfd adhere to device endianness

[Qemu-devel] [PATCH] Memory-API: Make eventfd adhere to device endianness

[Alexander Graf]

Our memory API MMIO regions know the concept of device endianness. This
is used to automatically swap endianness between devices and host CPU,
depending on whether buses in between would swizzle the bits.

The ioeventfd value comparison does not adhere to that semantic though.
Probably because nobody has been running ioeventfd on a BE platform and
the only device implementing ioeventfd right now is LE (PCI) based.

So add swizzling to ioeventfd registration / deletion to make the rest
of the code as consistent as possible.

Thanks a lot to Michael Tsirkin to point me towards the right direction.

Signed-off-by: Alexander Graf <agraf@suse.de>
---
 memory.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/memory.c b/memory.c
index 4f3ade0..d2f2fd6 100644
--- a/memory.c
+++ b/memory.c
@@ -1217,6 +1217,7 @@ void memory_region_add_eventfd(MemoryRegion *mr,
     };
     unsigned i;
 
+    adjust_endianness(mr, &mrfd.data, size);
     memory_region_transaction_begin();
     for (i = 0; i < mr->ioeventfd_nb; ++i) {
         if (memory_region_ioeventfd_before(mrfd, mr->ioeventfds[i])) {
@@ -1248,6 +1249,7 @@ void memory_region_del_eventfd(MemoryRegion *mr,
     };
     unsigned i;
 
+    adjust_endianness(mr, &mrfd.data, size);
     memory_region_transaction_begin();
     for (i = 0; i < mr->ioeventfd_nb; ++i) {
         if (memory_region_ioeventfd_equal(mrfd, mr->ioeventfds[i])) {
-- 
1.6.0.2

Re: [Qemu-devel] [PATCH] Memory-API: Make eventfd adhere to device endianness

[Avi Kivity]

On 10/15/2012 08:30 PM, Alexander Graf wrote:
> Our memory API MMIO regions know the concept of device endianness. This
> is used to automatically swap endianness between devices and host CPU,
> depending on whether buses in between would swizzle the bits.
> 
> The ioeventfd value comparison does not adhere to that semantic though.
> Probably because nobody has been running ioeventfd on a BE platform and
> the only device implementing ioeventfd right now is LE (PCI) based.
> 
> So add swizzling to ioeventfd registration / deletion to make the rest
> of the code as consistent as possible.
> 
> Thanks a lot to Michael Tsirkin to point me towards the right direction.

Thanks, applied.


-- 
error compiling committee.c: too many arguments to function