KVM: SVM: Don't call instruction emulator for invd and wbinvd
in [Kernel]
|
Prev: Regarding the rt2860sta module
Next: [PATCH 2/2] x86: add HPET-quirk for nVidia MCP61 LPC Bridge (10de:03e0)
From: Avi Kivity on 21 Feb 2010 07:10 On 02/21/2010 01:37 PM, Joerg Roedel wrote: > On Sun, Feb 21, 2010 at 11:53:14AM +0200, Avi Kivity wrote: > >> On 02/19/2010 05:23 PM, Joerg Roedel wrote: >> >>> There is an intercept for WBINVD and INVD in SVM so we don't >>> need the instruction emulator. The primary reason is that >>> the current instruction emulator fails to emulate these >>> instructions and the rip is not advanced. >>> >>> >> The bios (at least bochs bios) does have wbinvd, so this ought to work. >> > Weird. For some reason the Windows 7 XP emulation was executing wbinvd > which caused an nested intercept for the host level and the rip was not > advanced. So the nested guest did not advance and just produces wbinvd > intercepts all the time. > Has the guest enabled wbinvd interception? Perhaps not, so kvm has to emulate wbinvd in the nested guest context, which is likely the only case that we're called to do this. So the problem might be in emulating within the nested guest. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |