Ingo Molnar wrote: > * Avi Kivity <[EMAIL PROTECTED]> wrote: > > >>> Is there no cheap way to do this flushing preemptively (say in >>> vcpu_put()), to make the VM context potentially loadable into another >>> CPU? >>> >> You could issue a vmclear, but that forces a vm entry on the _same_ >> cpu to use vmlaunch instead of vmresume, which is documented as >> expensive. >> > > hm. Could you try to just do a vmresume nevertheless - maybe it works > but is undocumented?
I'd hate to do that. There are at least three implementations of VT (PD, Core, Core2) and maybe more when steppings and microcode updates are considered. Not to mention having kvm fail when a new cpu is introduced is not a pleasant scenario. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
