From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Guest debugging support for KVM
Date: Thu, 15 Jan 2009 22:26:45 +0100 [thread overview]
Message-ID: <496FAA15.806@web.de> (raw)
In-Reply-To: <496F9A59.4040503@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 2322 bytes --]
Anthony Liguori wrote:
> Jan Kiszka wrote:
>> [ Also available via git://git.kiszka.org/qemu.git queue/gdb ]
>>
>> 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
>>
>> Open issues: Writing soft breakpoints to BIOS code. cpu_memory_rw_debug
>> does not work here. Suggestion to fix this cleanly are welcome.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> configure | 4 +
>> exec.c | 10 ++-
>> gdbstub.c | 29 +++++++--
>> gdbstub.h | 7 ++
>> kvm-all.c | 172
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> kvm.h | 41 +++++++++++++
>> target-i386/kvm.c | 172
>> +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 7 files changed, 423 insertions(+), 12 deletions(-)
>>
>> diff --git a/configure b/configure
>> index a8ea55a..afbe1e0 100755
>> --- a/configure
>> +++ b/configure
>> @@ -479,11 +479,11 @@ case "$cpu" in
>> ARCH_CFLAGS="-march=z900"
>> ;;
>> i386)
>> - ARCH_CFLAGS="-m32"
>> + ARCH_CFLAGS="-m32 -DCONFIG_X86"
>> ARCH_LDFLAGS="-m32"
>> ;;
>> x86_64)
>> - ARCH_CFLAGS="-m64"
>> + ARCH_CFLAGS="-m64 -DCONFIG_X86"
>> ARCH_LDFLAGS="-m64"
>> ;;
>> esac
>>
>
> This seems unnecessary, no?
Nope. I suggested and Avi merged a patch to define
KVM_CAP_SET_GUEST_DEBUG only for those archs (ie. currently x86) that
really support it. That avoids having to define empty stubs on the other
KVM archs.
So we need to define the proper arch switch to make the CAP appear in
the kernel header. Also note that there are much more conditional CAP
defines queued up or already merged into mainline.
>
> The rest looks good.
>
> Regards,
>
> Anthony Liguori
>
>
>
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-01-15 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 14:43 [Qemu-devel] [PATCH] Guest debugging support for KVM Jan Kiszka
2009-01-15 20:19 ` Anthony Liguori
2009-01-15 21:26 ` Jan Kiszka [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=496FAA15.806@web.de \
--to=jan.kiszka@web.de \
--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).