From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 65561] KVM:Entry failed on Single stepping sti instruction
Date: Sat, 24 May 2014 05:38:16 +0000 [thread overview]
Message-ID: <bug-65561-28872-EyLVmPMujQ@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 #20 from Jidong Xiao <jidong.xiao@gmail.com> ---
Thanks Jatin, I actually tried some other instructions, like accessing cr
register. I use the following program:
linux:~/code/cvedr # cat getcr.c
#include <stdio.h>
main(){
asm __volatile__ (
"mov %cr0, %eax\n"
"mov %cr3, %ebx\n"
);
printf("test cr\n");
}
In x86_emulate_insn(), there is a piece of code like this (the printk is added
by me.)
==================================
case 0x20: /* mov cr, reg */
printk(KERN_ERR "DEBUG: Passed %s %d
\n",__FUNCTION__,__LINE__);
if (c->modrm_mod != 3)
goto cannot_emulate;
c->regs[c->modrm_rm] =
realmode_get_cr(ctxt->vcpu, c->modrm_reg);
c->dst.type = OP_NONE; /* no writeback */
break;
==================================
My results show that the above c program does not trigger this printk statement
neither. I assume accessing cr should be a privileged operation, right? So I am
really curious that how to trigger these printk statements?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-05-24 5:38 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 [this message]
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
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-EyLVmPMujQ@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