From: Paolo Bonzini <pbonzini@redhat.com>
To: Yang Weijiang <weijiang.yang@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
sean.j.christopherson@intel.com
Subject: Re: [PATCH] selftests: kvm: Fix assert failure in single-step test
Date: Wed, 23 Sep 2020 16:24:13 +0200 [thread overview]
Message-ID: <076c24ae-948a-48ed-99ec-c7d43753c802@redhat.com> (raw)
In-Reply-To: <20200826015524.13251-1-weijiang.yang@intel.com>
On 26/08/20 03:55, Yang Weijiang wrote:
> This is a follow-up patch to fix an issue left in commit:
> 98b0bf02738004829d7e26d6cb47b2e469aaba86
> selftests: kvm: Use a shorter encoding to clear RAX
>
> With the change in the commit, we also need to modify "xor" instruction
> length from 3 to 2 in array ss_size accordingly to pass below check:
>
> 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.arch.debugreg[7] = 0x00000400;
> APPLY_DEBUG();
> vcpu_run(vm, VCPU_ID);
> TEST_ASSERT(run->exit_reason == KVM_EXIT_DEBUG &&
> run->debug.arch.exception == DB_VECTOR &&
> run->debug.arch.pc == target_rip &&
> run->debug.arch.dr6 == target_dr6,
> "SINGLE_STEP[%d]: exit %d exception %d rip 0x%llx "
> "(should be 0x%llx) dr6 0x%llx (should be 0x%llx)",
> i, run->exit_reason, run->debug.arch.exception,
> run->debug.arch.pc, target_rip, run->debug.arch.dr6,
> target_dr6);
> }
>
> Reported-by: kernel test robot <rong.a.chen@intel.com>
> Signed-off-by: Yang Weijiang <weijiang.yang@intel.com>
> ---
> tools/testing/selftests/kvm/x86_64/debug_regs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/kvm/x86_64/debug_regs.c b/tools/testing/selftests/kvm/x86_64/debug_regs.c
> index b8d14f9db5f9..2fc6b3af81a1 100644
> --- a/tools/testing/selftests/kvm/x86_64/debug_regs.c
> +++ b/tools/testing/selftests/kvm/x86_64/debug_regs.c
> @@ -73,7 +73,7 @@ int main(void)
> int i;
> /* Instruction lengths starting at ss_start */
> int ss_size[4] = {
> - 3, /* xor */
> + 2, /* xor */
> 2, /* cpuid */
> 5, /* mov */
> 2, /* rdmsr */
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-09-23 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 1:55 Yang Weijiang
2020-09-23 14:24 ` Paolo Bonzini [this message]
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=076c24ae-948a-48ed-99ec-c7d43753c802@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=weijiang.yang@intel.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
all inboxes | Powered by JetHome®