On Thu, Jul 10, 2008 at 05:57:56PM +0300, Avi Kivity wrote: > It makes sense to initialize VT-d before. Since memslots can be > created and destroyed dynamically, with the current implementation > we can see > > create slot > create slot > init VT-d > create slot > > which means we need to support both slot-creation-after-VT-d and > init-VT-d-after-slot-creation. If we initialize VT-d up front, we > only need to support (and test) one scenario.
Fair enough---we'll take a look at whether initializing VT-d first introduces any complications other than hot-plug (see below). > On the other hand, this means that you will not be able to assign > devices unless you specified this when creating the VM; but I think > this is fair. It will be nice to support hot-plugged pass-through devices some time in the future. Cheers, Muli -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
