Joerg Roedel wrote: > Generally I see no problem with it. But at least for NPT I don't see a > reason why someone should want to disable it on a VM basis (as far as it > works stable). Avi, what do you think? >
Unless there is a real-life workload that benefits from npt=0, I see no reason to have per-vm npt control. The module parameter is helpful, for to isolate npt problems and for development, but I don't see a need for users to fiddle with it. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- 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