Re: Event channels in KVM?

[Avi Kivity <avi@redhat.com>]

Matt Anger wrote:
> Thanks for the info, I've been looking into it by trying to look
> around kvm source code.
> Apparently I have to write a kernel driver for the guest os and then
> also write backend driver and modify qemu to use it? Is that correct?
> That seems ugly, especially since now my io goes guest->guest kernel
> driver->host kernel kvm->qemu->host kernel driver....
> With Xen event-channels my driver gets the event notification directly
> with no user space intervention removing the middle 2 steps and I
> don't have to touch any of Xen's codebase. My driver just registers
> for an event-channel.
>   

The qemu device in kvm is equivalent to the dom0 backend driver.
kvm's qemu is equivalent to Xen's dom0.
The guest kernel driver in kvm is equivalent to the domU kernel driver.
Event channels map to interrupts (host->guest) and mmio/pio 
(guest/host); virtio provides an abstraction on top of that.

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