From: Maxim Levitsky <mlevitsk@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Cc: Kieran Bingham <kbingham@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Andrew Jones <drjones@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Sean Christopherson <seanjc@google.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Johannes Berg <johannes.berg@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jessica Yu <jeyu@kernel.org>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Yang Weijiang <weijiang.yang@intel.com>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 6/6] KVM: selftests: test KVM_GUESTDBG_BLOCKIRQ
Date: Mon, 01 Nov 2021 18:19:09 +0200 [thread overview]
Message-ID: <b48210a35b3bc6d63beeb33c19b609b3014191dd.camel@redhat.com> (raw)
In-Reply-To: <87sfwfkhk5.fsf@vitty.brq.redhat.com>
On Mon, 2021-11-01 at 16:43 +0100, Vitaly Kuznetsov wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
> > On 11/08/21 14:29, Maxim Levitsky wrote:
> > > Modify debug_regs test to create a pending interrupt
> > > and see that it is blocked when single stepping is done
> > > with KVM_GUESTDBG_BLOCKIRQ
> > >
> > > Signed-off-by: Maxim Levitsky <mlevitsk@redhat.com>
> > > ---
> > > .../testing/selftests/kvm/x86_64/debug_regs.c | 24 ++++++++++++++++---
> > > 1 file changed, 21 insertions(+), 3 deletions(-)
> >
> > I haven't looked very much at this, but the test fails.
> >
>
> Same here,
>
> the test passes on AMD but fails consistently on Intel:
>
> # ./x86_64/debug_regs
> ==== Test Assertion Failure ====
> x86_64/debug_regs.c:179: run->exit_reason == KVM_EXIT_DEBUG && run->debug.arch.exception == DB_VECTOR && run->debug.arch.pc == target_rip && run->debug.arch.dr6 == target_dr6
> pid=13434 tid=13434 errno=0 - Success
> 1 0x00000000004027c6: main at debug_regs.c:179
> 2 0x00007f65344cf554: ?? ??:0
> 3 0x000000000040294a: _start at ??:?
> SINGLE_STEP[1]: exit 8 exception 1 rip 0x402a25 (should be 0x402a27) dr6 0xffff4ff0 (should be 0xffff4ff0)
>
> (I know I'm late to the party).
Well that is strange. It passes on my intel laptop. Just tested
(kvm/queue + qemu master, compiled today) :-(
It fails on iteration 1 (and there is iteration 0) which I think means that we
start with RIP on sti, and get #DB on start of xor instruction first (correctly),
and then we get #DB again on start of xor instruction again?
Something very strange. My laptop has i7-7600U.
Best regards,
Maxim Levitsky
>
> > Paolo
> >
> > > diff --git a/tools/testing/selftests/kvm/x86_64/debug_regs.c b/tools/testing/selftests/kvm/x86_64/debug_regs.c
> > > index 6097a8283377..5f078db1bcba 100644
> > > --- a/tools/testing/selftests/kvm/x86_64/debug_regs.c
> > > +++ b/tools/testing/selftests/kvm/x86_64/debug_regs.c
> > > @@ -8,12 +8,15 @@
> > > #include <string.h>
> > > #include "kvm_util.h"
> > > #include "processor.h"
> > > +#include "apic.h"
> > >
> > > #define VCPU_ID 0
> > >
> > > #define DR6_BD (1 << 13)
> > > #define DR7_GD (1 << 13)
> > >
> > > +#define IRQ_VECTOR 0xAA
> > > +
> > > /* For testing data access debug BP */
> > > uint32_t guest_value;
> > >
> > > @@ -21,6 +24,11 @@ extern unsigned char sw_bp, hw_bp, write_data, ss_start, bd_start;
> > >
> > > static void guest_code(void)
> > > {
> > > + /* Create a pending interrupt on current vCPU */
> > > + x2apic_enable();
> > > + x2apic_write_reg(APIC_ICR, APIC_DEST_SELF | APIC_INT_ASSERT |
> > > + APIC_DM_FIXED | IRQ_VECTOR);
> > > +
> > > /*
> > > * Software BP tests.
> > > *
> > > @@ -38,12 +46,19 @@ static void guest_code(void)
> > > "mov %%rax,%0;\n\t write_data:"
> > > : "=m" (guest_value) : : "rax");
> > >
> > > - /* Single step test, covers 2 basic instructions and 2 emulated */
> > > + /*
> > > + * Single step test, covers 2 basic instructions and 2 emulated
> > > + *
> > > + * Enable interrupts during the single stepping to see that
> > > + * pending interrupt we raised is not handled due to KVM_GUESTDBG_BLOCKIRQ
> > > + */
> > > asm volatile("ss_start: "
> > > + "sti\n\t"
> > > "xor %%eax,%%eax\n\t"
> > > "cpuid\n\t"
> > > "movl $0x1a0,%%ecx\n\t"
> > > "rdmsr\n\t"
> > > + "cli\n\t"
> > > : : : "eax", "ebx", "ecx", "edx");
> > >
> > > /* DR6.BD test */
> > > @@ -72,11 +87,13 @@ int main(void)
> > > uint64_t cmd;
> > > int i;
> > > /* Instruction lengths starting at ss_start */
> > > - int ss_size[4] = {
> > > + int ss_size[6] = {
> > > + 1, /* sti*/
> > > 2, /* xor */
> > > 2, /* cpuid */
> > > 5, /* mov */
> > > 2, /* rdmsr */
> > > + 1, /* cli */
> > > };
> > >
> > > if (!kvm_check_cap(KVM_CAP_SET_GUEST_DEBUG)) {
> > > @@ -154,7 +171,8 @@ int main(void)
> > > for (i = 0; i < (sizeof(ss_size) / sizeof(ss_size[0])); i++) {
> > > target_rip += ss_size[i];
> > > CLEAR_DEBUG();
> > > - debug.control = KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_SINGLESTEP;
> > > + debug.control = KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_SINGLESTEP |
> > > + KVM_GUESTDBG_BLOCKIRQ;
> > > debug.arch.debugreg[7] = 0x00000400;
> > > APPLY_DEBUG();
> > > vcpu_run(vm, VCPU_ID);
> > >
next prev parent reply other threads:[~2021-11-01 16:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 12:29 [PATCH v3 0/6] KVM: my debug patch queue Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 1/6] KVM: SVM: split svm_handle_invalid_exit Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 2/6] KVM: x86: add force_intercept_exceptions_mask Maxim Levitsky
2021-09-02 16:56 ` Sean Christopherson
2022-02-08 14:34 ` Maxim Levitsky
2022-03-08 23:37 ` Sean Christopherson
2022-03-09 12:31 ` Maxim Levitsky
2022-03-09 14:03 ` Paolo Bonzini
2022-03-09 15:40 ` Sean Christopherson
2021-08-11 12:29 ` [PATCH v3 3/6] KVM: SVM: implement force_intercept_exceptions_mask Maxim Levitsky
2021-08-11 14:26 ` Maxim Levitsky
2021-09-02 17:34 ` Sean Christopherson
2022-02-08 14:35 ` Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 4/6] scripts/gdb: rework lx-symbols gdb script Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 5/6] KVM: x86: implement KVM_GUESTDBG_BLOCKIRQ Maxim Levitsky
2021-08-11 12:29 ` [PATCH v3 6/6] KVM: selftests: test KVM_GUESTDBG_BLOCKIRQ Maxim Levitsky
2021-09-06 11:20 ` Paolo Bonzini
2021-09-06 21:03 ` Maxim Levitsky
2021-11-01 15:43 ` Vitaly Kuznetsov
2021-11-01 16:19 ` Maxim Levitsky [this message]
2021-11-01 23:21 ` Sean Christopherson
2021-11-02 10:46 ` Vitaly Kuznetsov
2021-11-02 15:53 ` Sean Christopherson
2021-11-02 16:18 ` Vitaly Kuznetsov
2021-11-02 18:45 ` Sean Christopherson
2021-11-03 9:04 ` Maxim Levitsky
2021-08-11 13:10 ` [PATCH v3 0/6] KVM: my debug patch queue Paolo Bonzini
2021-08-11 13:22 ` Maxim Levitsky
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=b48210a35b3bc6d63beeb33c19b609b3014191dd.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=drjones@redhat.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jeyu@kernel.org \
--cc=jmattson@google.com \
--cc=johannes.berg@intel.com \
--cc=joro@8bytes.org \
--cc=kbingham@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=weijiang.yang@intel.com \
--cc=x86@kernel.org \
/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).