From: Sheng Yang <sheng@linux.intel.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Add missing emulation failure report in kvm_mmu_page_fault()
Date: Tue, 19 Jan 2010 16:05:26 +0800 [thread overview]
Message-ID: <201001191605.26389.sheng@linux.intel.com> (raw)
In-Reply-To: <20100119075757.GJ14345@redhat.com>
On Tuesday 19 January 2010 15:57:57 Gleb Natapov wrote:
> On Tue, Jan 19, 2010 at 09:54:44AM +0200, Avi Kivity wrote:
> > On 01/19/2010 05:06 AM, Sheng Yang wrote:
> > >>There are two problems with the kernel failure report. First, it
> > >>doesn't report enough data - registers, surrounding instructions, etc.
> > >>that are needed to explain what is going on. Second, it can flood
> > >>dmesg, which is a pretty bad thing to do.
> > >
> > >When you talking about "built-in disassembler", do you talking about
> > >"memsave/objdump" or some other more convenient way for this?
> > >
> > >And maybe we can let QEmu do some dump of the assembler code?
> > >(kvm_show_code())
> >
> > In the qemu monitor, type 'x/20i $eip' to get a disassembly of code
> > around the current instruction pointer.
>
> If you want to see code _around_ the current instruction pointer type
> 'x/20i $eip-20' :) Or that is what I usually do.
Oh, damn, indeed very convenient...
Thanks you all for this good tip. :)
--
regards
Yang, Sheng
prev parent reply other threads:[~2010-01-19 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 8:44 [PATCH] KVM: Add missing emulation failure report in kvm_mmu_page_fault() Sheng Yang
2010-01-17 12:34 ` Avi Kivity
2010-01-18 9:32 ` Sheng Yang
2010-01-18 11:32 ` Avi Kivity
2010-01-19 3:06 ` Sheng Yang
2010-01-19 7:54 ` Avi Kivity
2010-01-19 7:57 ` Gleb Natapov
2010-01-19 8:05 ` Sheng Yang [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=201001191605.26389.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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