On Friday 21 March 2008 01:11:35 Anthony Liguori wrote: > Rusty Russell wrote: > > There are three possible solutions: > > 1) Just offer the lowest common denominator to both sides (ie. no > > features). This is what I do with lguest in these patches. > > 2) Offer something and handle the case where one Guest accepts and > > another doesn't by emulating it. ie. de-TSO the packets manually. > > 3) "Hot unplug" the device from the guest which asks for the greater > > features, then re-add it offering less features. Requires hotplug in the > > guest OS. > > 4) Add a feature negotiation feature. The feature that gets set is the > "feature negotiate" feature. If a guest doesn't support feature > negotiation, you end up with the least-common denominator (no > features). If both guests support feature negotiation, you can then add > something new to determine the true common subset.
Hmm, I discarded that out of hand as too icky, but we might end up there. Analyse features like normal, accept feature negotiation, set DRIVER_OK, wait for config change, if feature negotiation is still set then go around again (presumably some features have been removed). I'll prototype it and see how we go. Thanks, Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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
