On 6/7/07, Avi Kivity <[EMAIL PROTECTED]> wrote: > 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 >
Avi, may you explain what is the role of the "bus interface" in the whole picture? To autodetect and probe new virtual device?? About the balloon driver, I looked at the current code, and what I dont like is its approach: it needs to be operated from inside the guest, which is not the way we usually want to do. So something like Xen balloon driver is certainly better. Dor, why dont you get the idea from Xen balloon, but take your way? Thanks, Jun ------------------------------------------------------------------------- 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
