Alex Williamson reported that a Windows game does something weird that makes the guest save and restore debug registers on each context switch. This cause several hundred thousands vmexits per second, and basically cuts performance in half when running under KVM. However, when not running in guest-debug mode, the guest controls the debug registers and having to take an exit for each DR access is a waste of time. We just need one vmexit to load any stale values of DR0-DR6, and then we can let the guest run freely. On the next vmexit (whatever the reason) we will read out whatever changes the guest made to the debug registers. Tested with x86/debug.flat on both Intel and AMD, both direct and nested virtualization. Changes from RFC: changed get_dr7 callback to sync_dirty_debug_regs, new patches 5-7. Paolo Bonzini (7): KVM: vmx: we do rely on loading DR7 on entry KVM: x86: change vcpu->arch.switch_db_regs to a bit mask KVM: x86: Allow the guest to run with dirty debug registers KVM: vmx: Allow the guest to run with dirty debug registers KVM: nVMX: Allow nested guests to run with dirty debug registers KVM: svm: set/clear all DR intercepts in one swoop KVM: svm: Allow the guest to run with dirty debug registers arch/x86/include/asm/kvm_host.h | 8 ++++- arch/x86/kvm/svm.c | 68 ++++++++++++++++++++++++++++------------- arch/x86/kvm/vmx.c | 43 ++++++++++++++++++++++++-- arch/x86/kvm/x86.c | 20 +++++++++++- 4 files changed, 114 insertions(+), 25 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
