LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@linux.alibaba.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH V2 3/3] KVM: X86: Reset DR6 only when KVM_DEBUGREG_WONT_EXIT
Date: Tue, 10 Aug 2021 18:34:54 +0800 [thread overview]
Message-ID: <7a1ca89f-7b4e-7df2-e47a-ac5207137a05@linux.alibaba.com> (raw)
In-Reply-To: <f07b99f1-5a25-a246-9ef9-2b875d960675@redhat.com>
On 2021/8/10 18:14, Paolo Bonzini wrote:
> On 09/08/21 19:43, Lai Jiangshan wrote:
>> From: Lai Jiangshan <laijs@linux.alibaba.com>
>>
>> The commit efdab992813fb ("KVM: x86: fix escape of guest dr6 to the host")
>> fixed a bug by reseting DR6 unconditionally when the vcpu being scheduled out.
>>
>> But writing to debug registers is slow, and it can be shown in perf results
>> sometimes even neither the host nor the guest activate breakpoints.
>>
>> It'd be better to reset it conditionally and this patch moves the code of
>> reseting DR6 to the path of VM-exit and only reset it when
>> KVM_DEBUGREG_WONT_EXIT which is the only case that DR6 is guest value.
>>
>> Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
>> ---
>> arch/x86/kvm/x86.c | 8 ++------
>> 1 file changed, 2 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index d2aa49722064..f40cdd7687d8 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -4309,12 +4309,6 @@ void kvm_arch_vcpu_put(struct kvm_vcpu *vcpu)
>> static_call(kvm_x86_vcpu_put)(vcpu);
>> vcpu->arch.last_host_tsc = rdtsc();
>> - /*
>> - * If userspace has set any breakpoints or watchpoints, dr6 is restored
>> - * on every vmexit, but if not, we might have a stale dr6 from the
>> - * guest. do_debug expects dr6 to be cleared after it runs, do the same.
>> - */
>> - set_debugreg(0, 6);
>> }
>> static int kvm_vcpu_ioctl_get_lapic(struct kvm_vcpu *vcpu,
>> @@ -9630,6 +9624,8 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
>> static_call(kvm_x86_sync_dirty_debug_regs)(vcpu);
>> kvm_update_dr0123(vcpu);
>> kvm_update_dr7(vcpu);
>> + /* Reset Dr6 which is guest value. */
>> + set_debugreg(DR6_RESERVED, 6);
>> }
>> /*
>>
>
> ... and this should also be done exclusively for VMX, in vmx_sync_dirty_debug_regs:
>
> KVM: VMX: Reset DR6 only when KVM_DEBUGREG_WONT_EXIT
> The commit efdab992813fb ("KVM: x86: fix escape of guest dr6 to the host")
> fixed a bug by resetting DR6 unconditionally when the vcpu being scheduled out.
> But writing to debug registers is slow, and it can be visible in perf results
> sometimes, even if neither the host nor the guest activate breakpoints.
> Since KVM_DEBUGREG_WONT_EXIT on Intel processors is the only case
> where DR6 gets the guest value, and it never happens at all on SVM,
> the register can be cleared in vmx.c right after reading it.
> Reported-by: Lai Jiangshan <laijs@linux.alibaba.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index 21a3ef3012cf..3a91302d05c0 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -5110,6 +5110,12 @@ static void vmx_sync_dirty_debug_regs(struct kvm_vcpu *vcpu)
>
> vcpu->arch.switch_db_regs &= ~KVM_DEBUGREG_WONT_EXIT;
> exec_controls_setbit(to_vmx(vcpu), CPU_BASED_MOV_DR_EXITING);
> +
> + /*
> + * do_debug expects dr6 to be cleared after it runs, avoid that it sees
> + * a stale dr6 from the guest.
> + */
do_debug() is renamed. Maybe you can use "The host kernel #DB handler".
> + set_debugreg(DR6_RESERVED, 6);
> }
>
> static void vmx_set_dr7(struct kvm_vcpu *vcpu, unsigned long val)
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index fbc536b21585..04c393551fb0 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4313,12 +4313,6 @@ void kvm_arch_vcpu_put(struct kvm_vcpu *vcpu)
>
> static_call(kvm_x86_vcpu_put)(vcpu);
> vcpu->arch.last_host_tsc = rdtsc();
> - /*
> - * If userspace has set any breakpoints or watchpoints, dr6 is restored
> - * on every vmexit, but if not, we might have a stale dr6 from the
> - * guest. do_debug expects dr6 to be cleared after it runs, do the same.
> - */
> - set_debugreg(0, 6);
> }
>
> static int kvm_vcpu_ioctl_get_lapic(struct kvm_vcpu *vcpu,
>
>
> Paolo
next prev parent reply other threads:[~2021-08-10 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 23:29 [PATCH] KVM: X86: Don't reset dr6 unconditionally when the vcpu being scheduled out Lai Jiangshan
2021-08-09 16:54 ` Sean Christopherson
2021-08-09 17:43 ` [PATCH V2 1/3] KVM: X86: Remove unneeded KVM_DEBUGREG_RELOAD Lai Jiangshan
2021-08-09 17:43 ` [PATCH V2 2/3] KVM: X86: Set the hardware DR6 only when KVM_DEBUGREG_WONT_EXIT Lai Jiangshan
2021-08-10 10:07 ` Paolo Bonzini
2021-08-10 10:30 ` Lai Jiangshan
2021-08-10 10:35 ` Paolo Bonzini
2021-08-10 10:46 ` Lai Jiangshan
2021-08-10 12:49 ` Paolo Bonzini
2021-08-09 17:43 ` [PATCH V2 3/3] KVM: X86: Reset " Lai Jiangshan
2021-08-10 9:42 ` Paolo Bonzini
2021-08-10 10:14 ` Paolo Bonzini
2021-08-10 10:34 ` Lai Jiangshan [this message]
2021-08-10 10:41 ` Paolo Bonzini
2021-08-10 9:59 ` [PATCH] KVM: X86: Don't reset dr6 unconditionally when the vcpu being scheduled out Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a1ca89f-7b4e-7df2-e47a-ac5207137a05@linux.alibaba.com \
--to=laijs@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jiangshanlai@gmail.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--subject='Re: [PATCH V2 3/3] KVM: X86: Reset DR6 only when KVM_DEBUGREG_WONT_EXIT' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).