On 25.08.2011, at 00:37, Pekka Enberg wrote: > On 8/25/11 8:22 AM, Alexander Graf wrote: >> >> On 25.08.2011, at 00:11, Pekka Enberg wrote: >> >>> On Wed, 2011-08-24 at 23:52 -0500, Alexander Graf wrote: >>>>> Isn't ivshmem in QEMU? If so, then I don't think there isn't any >>>>> competition. How do you feel that these are competing? >>>> >>>> Well, it means that you will inside the guest have two different >>>> devices depending whether you're using QEMU or kvm-tool. I don't see >>>> the point in exposing different devices to the guest just because of >>>> NIH. Why should a guest care which device emulation framework you're >>>> using? >>> >>> It's a pretty special-purpose device that requires user configuration so >>> I don't consider QEMU compatibility to be mandatory. It'd be nice to >>> have but not something to bend over backwards for. >> >> Well, the nice thing is that you would get the guest side for free: >> >> http://gitorious.org/nahanni/guest-code/blobs/master/kernel_module/uio/uio_ivshmem.c >> >> You also didn't invent your own virtio protocol, no? :) > > No, because virtio drivers are in Linux kernel proper. Is ivshmem in the kernel tree > or planned to be merged at some point? *shrug* Let's ask Cam. Alex -- 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
