I came across this thread looking for an efficient event channel mechanism between two guests (running on different cpu cores). While I can use available emulated IO mechanism (guest1->host kernel driver->Qemu1->Qemu2) in conjunction with interrupt mechanism (Qemu2->host kernel driver->guest2) in KVM, this involves several context switches. Xen handles notifications in hypervisor via hypercall and hence is likely more efficient. Is there a way I can perform direct notification (guest1->host kernel driver->guest2) in kvm? Thanks, Vivek. Matt Anger wrote: > I was referring to the bounce from host kernel to qemu > and then back > to the host kernel for my BE driver. > Xen: > guest -> guest kernel driver-> host kernel driver > > For both situations I need a FE and BE driver, but for > KVM I need to modify QEMU and teach it how to pass the > virtio calls to my Host > driver. In Xen BE driver and Host driver are the same and > I don't have > to recompile any part of Xen. > You can implement (host) kernel level device model too which will have same result with Xen, i.e. skip Qemu. I don't think Xen & KVM has fundamental difference here, but different implementation style. Xen implement BE driver in driver domain kernel, but KVM like to implement in user level host process. Different people has different favorite, I am neutral actually :) Thx, eddie -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo <at> vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html <http://vger.kernel.org/majordomo-info.html> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
