From: Andrey Wagin <avagin@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Oleg Nesterov <oleg@redhat.com>,
"criu@openvz.org" <criu@openvz.org>,
kvm@vger.kernel.org
Subject: Re: x86: Hardware breakpoints are not always triggered
Date: Thu, 28 Jan 2016 14:42:25 -0800 [thread overview]
Message-ID: <20160128224224.GA10028@gmail.com> (raw)
In-Reply-To: <56AA8928.50507@redhat.com>
On Thu, Jan 28, 2016 at 10:33:28PM +0100, Paolo Bonzini wrote:
>
>
> On 28/01/2016 09:31, Andrey Wagin wrote:
> > I tried to print drX registers after a break-point. Looks like they
> > are set correctly.
>
> Can you try this KVM patch?
Looks like it fixes a case when reproducers are running only in VM.
If I execute the reproducer a few times on the host and then execute it
in VM, it exits very fast.
Thanks,
Andrew
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index c13a64b7d789..32bae1c70a50 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -1612,6 +1612,7 @@ static void svm_sync_dirty_debug_regs(struct kvm_vcpu *vcpu)
> vcpu->arch.dr7 = svm->vmcb->save.dr7;
>
> vcpu->arch.switch_db_regs &= ~KVM_DEBUGREG_WONT_EXIT;
> + vcpu->arch.switch_db_regs |= KVM_DEBUGREG_RELOAD;
> set_dr_intercepts(svm);
> }
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index e2951b6edbbc..505a4663b9f4 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -5659,6 +5659,7 @@ static void vmx_sync_dirty_debug_regs(struct kvm_vcpu *vcpu)
> vcpu->arch.dr7 = vmcs_readl(GUEST_DR7);
>
> vcpu->arch.switch_db_regs &= ~KVM_DEBUGREG_WONT_EXIT;
> + vcpu->arch.switch_db_regs |= KVM_DEBUGREG_RELOAD;
>
> cpu_based_vm_exec_control = vmcs_read32(CPU_BASED_VM_EXEC_CONTROL);
> cpu_based_vm_exec_control |= CPU_BASED_MOV_DR_EXITING;
>
> Paolo
next prev parent reply other threads:[~2016-01-28 22:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:31 x86: Hardware breakpoints are not always triggered Andrey Wagin
2016-01-28 11:01 ` Jan Kiszka
2016-01-28 20:53 ` Oleg Nesterov
2016-01-28 21:29 ` Paolo Bonzini
2016-01-28 22:01 ` Oleg Nesterov
2016-01-28 21:33 ` Paolo Bonzini
2016-01-28 22:42 ` Andrey Wagin [this message]
2016-01-29 22:21 ` [CRIU] " Andrew Vagin
2016-01-31 11:01 ` Paolo Bonzini
2016-02-03 18:18 ` Nadav Amit
2016-02-03 23:32 ` Nadav Amit
2016-02-04 11:28 ` 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=20160128224224.GA10028@gmail.com \
--to=avagin@gmail.com \
--cc=criu@openvz.org \
--cc=gorcunov@openvz.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=pbonzini@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).