kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Stuart Yoder <b08248@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>, kvm-ppc <kvm-ppc@vger.kernel.org>,
	kvm <kvm@vger.kernel.org>
Subject: Re: State of KVM guest debugging support on Power
Date: Thu, 03 Nov 2011 20:14:42 +0100	[thread overview]
Message-ID: <4EB2E822.3080702@web.de> (raw)
In-Reply-To: <CALRxmdBu85C7YP5veh0ewg5xNE0CF5yEdRgKg+s8Ne6TJvkU2A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On 2011-11-03 19:59, Stuart Yoder wrote:
> On Tue, Nov 1, 2011 at 9:22 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi there,
>>
>> I'm generating some slides on guest debugging via kvm. What's the
>> current state for Book-E and Book-S? Works out of box, mostly usable, or
>> to be implemented? Is anyone using it?
> 
> Are you talking about guest debug using the QEMU stub or using
> the virtual CPU's debug registers and interrupts?    For Freescale
> Book E we have both approaches working, and patches to be sent upstream
> soon.

It's good to see both features coming into mainline.

I'll talk about the former, ie. debugging without guest help/awareness
(virtual hardware debugger). Is gdb well prepared for it (all registers
available, real-mode support, etc.)?

Thanks,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2011-11-03 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 14:22 State of KVM guest debugging support on Power Jan Kiszka
2011-11-03 18:59 ` Stuart Yoder
2011-11-03 19:10   ` Alexander Graf
2011-11-03 19:14   ` Jan Kiszka [this message]
2011-11-04 16:11     ` Stuart Yoder

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=4EB2E822.3080702@web.de \
    --to=jan.kiszka@web.de \
    --cc=agraf@suse.de \
    --cc=b08248@gmail.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).