summaryrefslogtreecommitdiff
path: root/arch/mips/jazz
diff options
context:
space:
mode:
authorSean Christopherson <sean.j.christopherson@intel.com>2019-07-10 19:07:34 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2019-07-11 16:10:22 +0300
commitd7a08882a0a4b4e176691331ee3f492996579534 (patch)
treeecfa90d990e01fd7e80d5eaa3093348fcd27f7b0 /arch/mips/jazz
parent66bb8a065f5aedd4551d8d3fbce582972f65c2e1 (diff)
downloadlinux-d7a08882a0a4b4e176691331ee3f492996579534.tar.xz
KVM: x86: Unconditionally enable irqs in guest context
On VMX, KVM currently does not re-enable irqs until after it has exited the guest context. As a result, a tick that fires in the window between VM-Exit and guest_exit_irqoff() will be accounted as system time. While said window is relatively small, it's large enough to be problematic in some configurations, e.g. if VM-Exits are consistently occurring a hair earlier than the tick irq. Intentionally toggle irqs back off so that guest_exit_irqoff() can be used in lieu of guest_exit() in order to avoid the save/restore of flags in guest_exit(). On my Haswell system, "nop; cli; sti" is ~6 cycles, versus ~28 cycles for "pushf; pop <reg>; cli; push <reg>; popf". Fixes: f2485b3e0c6c0 ("KVM: x86: use guest_exit_irqoff") Reported-by: Wei Yang <w90p710@gmail.com> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/mips/jazz')
0 files changed, 0 insertions, 0 deletions