All of lore.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: Sat, 24 May 2014 05:43:33 +0000	[thread overview]
Message-ID: <bug-65561-28872-4VOw50IKJi@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 #21 from Jatin Kumar <jatin.iitdelhi@gmail.com> ---
The way I would approach this problem is to first check if there is a VM_EXIT
while executing this instruction. You should be able to find that in
vmx_vcpu_run() function (I guess in KVM code). Put a printk there and print the
instruction as well which caused VM_EXIT.

Futher you should try to investigate if the control flow is trying to emulate
this instruction and then your printk's should be triggered.

CAUTION: I haven't spent much time digging KVM code, but I am confident about
the VM_EXIT part. Still after putting in some effort, you may want to wait for
Paolo's reply :)

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

  parent reply	other threads:[~2014-05-24  5:43 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 [this message]
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-4VOw50IKJi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.