Re: [Qemu-devel] [PATCH 28/35] kvm: x86: Introduce kvmclock device to save/restore its state

[Avi Kivity]

On 01/19/2011 06:57 PM, Anthony Liguori wrote:
> On 01/19/2011 07:15 AM, Markus Armbruster wrote:
> > So they interact with KVM (need kvm_state), and they interact with the
> > emulated PCI bus.  Could you elaborate on the fundamental difference
> > between the two interactions that makes you choose the (hypothetical)
> > KVM bus over the PCI bus as device parent?
>
> It's almost arbitrary, but I would say it's the direction that I/Os flow.

In the case of kvm, things are somewhat misleading.  I/O still flows 
through the (virtual) PCI bus, it's just short-circuited to a real 
device.  Similarly when attaching an ioeventfd to a virtio kick 
register, things still logically from the same way as without ioeventfd; 
we simply add a fast path for the operation.  But it doesn't change the 
logical view of things.

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