>This attempts to implement a "virtual I/O" layer which should allow >common drivers to be efficiently used across most virtual I/O >mechanisms. It will no-doubt need further enhancement. > >The details of probing the device are left to hypervisor-specific >code: it simple constructs the "struct virtio_device" and hands it to >the probe function (eg. virtnet_probe() or virtblk_probe()). > >The virtio drivers add and detach input and output buffers; as the >buffers are used up their associated "used" pointers are filled in. > >I have written two virtio device drivers (net and block) and two >virtio implementations (for lguest): a read-write socket-style >implementation, and a more efficient descriptor-based implementation). > >Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
That's the exact things I was planning to add to KVM/Linux. All virtual I/O devices should have common interface and share the core functionality. Since Xen PV drivers are already performance optimized and feature rich, we were planning to generalize the hypervisor-specific backend in order to reuse them. This is a good step toward such sharing. Cheers, Dor. _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/virtualization
