public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 65561] KVM:Entry failed on Single stepping sti instruction
Date: Sun, 25 May 2014 06:46:13 +0000	[thread overview]
Message-ID: <bug-65561-28872-A99N7fLV9U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65561-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=65561

--- Comment #31 from Jidong Xiao <jidong.xiao@gmail.com> ---
Hi, Paolo,

I added a sti instruction in kvm-unit-tests:x86/debug.c, like this:
        asm volatile(
                "pushf\n\t"
                "pop %%rax\n\t"
                "sti\n\t"
                "or $(1<<8),%%rax\n\t"
                "push %%rax\n\t"
                "lea (%%rip),%0\n\t"
                "popf\n\t"
                "and $~(1<<8),%%rax\n\t"
                "push %%rax\n\t"
                "popf\n\t"
                : "=g" (start) : : "rax");
        report("single step",
               n == 3 &&
               bp_addr[0] == start+1+6 && dr6[0] == 0xffff4ff0 &&
               bp_addr[1] == start+1+6+1 && dr6[1] == 0xffff4ff0 &&
               bp_addr[2] == start+1+6+1+1 && dr6[2] == 0xffff4ff0);

And then make, and run the test, it looks like everything is okay.
linux:~/code/kvm-unit-tests # /usr/local2/bin/qemu-system-x86_64 -enable-kvm
-device pc-testdev -serial stdio -device isa-debug-exit,iobase=0xf4,iosize=0x4
-kernel ./x86/debug.flat
enabling apic
PASS: #BP
PASS: hw breakpoint
PASS: single step
PASS: hw watchpoint


I also tried to add a cli before sti, and the test also passed.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-05-25  6:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 17:27 [Bug 65561] New: KVM:Entry failed on Single stepping sti instruction bugzilla-daemon
2014-05-20  5:12 ` [Bug 65561] " bugzilla-daemon
2014-05-20  7:10 ` bugzilla-daemon
2014-05-20 11:03 ` bugzilla-daemon
2014-05-20 21:00 ` bugzilla-daemon
2014-05-21  4:43 ` bugzilla-daemon
2014-05-21  4:45 ` bugzilla-daemon
2014-05-21  7:13 ` bugzilla-daemon
2014-05-21 15:13 ` bugzilla-daemon
2014-05-21 15:20 ` bugzilla-daemon
2014-05-21 16:05 ` bugzilla-daemon
2014-05-21 16:30 ` bugzilla-daemon
2014-05-21 16:39 ` bugzilla-daemon
2014-05-21 16:50 ` bugzilla-daemon
2014-05-21 17:14 ` bugzilla-daemon
2014-05-21 20:30 ` bugzilla-daemon
2014-05-21 21:08 ` bugzilla-daemon
2014-05-22  2:02 ` bugzilla-daemon
2014-05-24  4:59 ` bugzilla-daemon
2014-05-24  5:27 ` bugzilla-daemon
2014-05-24  5:38 ` bugzilla-daemon
2014-05-24  5:43 ` bugzilla-daemon
2014-05-24  5:46 ` bugzilla-daemon
2014-05-24  5:51 ` bugzilla-daemon
2014-05-24  5:56 ` bugzilla-daemon
2014-05-24  6:15 ` bugzilla-daemon
2014-05-24  6:29 ` bugzilla-daemon
2014-05-24  7:24 ` bugzilla-daemon
2014-05-24 12:26 ` bugzilla-daemon
2014-05-24 23:12 ` bugzilla-daemon
2014-05-25  3:03 ` bugzilla-daemon
2014-05-25  6:46 ` bugzilla-daemon [this message]
2014-05-25  7:48 ` bugzilla-daemon
2014-05-25  7:58 ` bugzilla-daemon
2014-05-25  8:00 ` bugzilla-daemon

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=bug-65561-28872-A99N7fLV9U@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.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