From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 1/2] Guest debugging support for KVM
Date: Tue, 10 Mar 2009 18:19:57 +0200 [thread overview]
Message-ID: <f43fc5580903100919l17cfc578ne0f5e0d1353fd513@mail.gmail.com> (raw)
In-Reply-To: <49B433EE.4080704@web.de>
On 3/8/09, Jan Kiszka <jan.kiszka@web.de> wrote:
> This is a backport of the guest debugging support for the KVM
> accelerator that is now part of the KVM tree. It implements the reworked
> KVM kernel API for guest debugging (KVM_CAP_SET_GUEST_DEBUG) which is
> not yet part of any mainline kernel but will probably be 2.6.30 stuff.
> So far supported is x86, but PPC is expected to catch up soon.
>
> Core features are:
> - unlimited soft-breakpoints via code patching
> - hardware-assisted x86 breakpoints and watchpoints
The statically dimensioned arrays (hw_breakpoint[4], single
hw_watchpoint) make me wonder what would happen in the SMP case. Or is
only one CPU ever targeted at a time for debugging?
next prev parent reply other threads:[~2009-03-10 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 21:09 [Qemu-devel] [PATCH v3 1/2] Guest debugging support for KVM Jan Kiszka
2009-03-10 16:19 ` Blue Swirl [this message]
2009-03-10 16:51 ` [Qemu-devel] " Jan Kiszka
2009-03-12 20:13 ` Anthony Liguori
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=f43fc5580903100919l17cfc578ne0f5e0d1353fd513@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).