On (Wed) Jun 24 2009 [20:20:27], Jamie Lokier wrote: > Amit Shah wrote: > > > > I think the interface from the guest POV stays the same: reads / writes > > to char devices. With virtio-serial, though, we can add a few other > > interesting things like names to ports, ability to hot-add ports on > > demand, request notifications when either end goes down, etc. > > Good features, useful for a lot of handy things. I think it would be > handy if the same features were available to the guest application > generally, not just on guest kernels with a specific driver though. > > As we talked before, about things like boot loaders and kernel > debuggers, and installing the support applications on old guests. The -net vmchannel offers that option. Can't see how to do it other way. > Is it possible to support access to the same capabilities through a > well known IO/MMIO address, in the same way that VGA and IDE are both > ordinary PCI devices, but also can be reached easily through well > known IO/MMIO addresses in simple code? The exits caused by accessing IO/MMIO regions are costlier than using PV. So using the current vmchannel option would be almost similar in those respects. Also, virtio is the almost standard way these days to get performance. We already have block, net drivers over virtio and they have been ported to older kernels as well. Amit -- 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
