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

Reply via email to