Carsten Otte wrote: > The best approach into this direction I have seen so far is not our > own vdev thing but Rusty's virtio infrastructure. That's what I think > I would start with. > >
I agree. We need a Lego set containing the following bricks: - bus interfaces: pci bus, hypercall-based bus, xenbus - functionality: net driver, block driver - virtio data path: xen rings + grant tables + event channels, kvm rings + kmap_atomic + interrupts So you can write a 4-line driver that glues the pci bus interface to the net functionality driver to kvm virtio backend, and take the rest of the day off. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
