Rusty Russell wrote: >> >> A side effect of this is that Xen drivers can no longer use virtio. >> > > I'm not so sure. > > We were always assuming that Xen could do state management in its virtio > layer. If this is not true, it implies we need hooks in the virtio > drivers, and I don't think we've made it worse by making it translate > xenbus config info into virtio_config. >
This means writing a low-level ABI in terms of a high level API. And while that describes virtualization fairly will, I prefer not to do this more than strictly necessary. However, this can be rewritten if/when Xen or VMware show interest in porting their drivers to virtio. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
