Joerg Roedel wrote: > There is no danger for the host kernel but for the guest. If the > userspace sets the monitor bit the guest will receive an #UD when trying > to use it. And we don't want the guest to use it because it is not > virtualized yet. >
So, isn't a simpler fix not to set the monitor bit in cpuid? The patch is correct, but I don't see why it's needed as any guest will check the cpuid bit before using monitor. -- 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
