From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Hollis Blanchard <hollisb@us.ibm.com>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 2/5] KVM: New guest debug interface
Date: Mon, 08 Dec 2008 10:42:34 +0100 [thread overview]
Message-ID: <493CEC0A.7000505@siemens.com> (raw)
In-Reply-To: <493CEA10.2000104@redhat.com>
Avi Kivity wrote:
> Jan Kiszka wrote:
>>>> Note that both SVM and VTX are supported, but only the latter was
>>>> tested
>>>> yet. Based on the experience with all those VTX corner case, I would be
>>>> fairly surprised if SVM will work out of the box.
>>>>
>>>>
>>> I'd like svm to work before applying.
>>>
>>
>> To validate the design?
>>
>>
>
> To make sure it doesn't oops, and to make sure it works.
>
>> I will see if I can organize an SVM box, but I can't promise when I'll
>> be able to do the testing. Anyone willing to contribute time on this
>> would be warmly welcome!
>>
>>
>
> I happen to have an svm box. How do you test this? play with gdb inside
> and outside the guest?
For inside the box, I also use the kgdb testsuite (kgbts).
For guest debugging check, some manual interaction is required: Set a
breakpoint on a prominent symbol (my favorite is sys_execve), do some
single stepping, check that smp works (breakpoint hits on all vcpus),
add some watchpoint and check if it triggers at reasonable spots (I
recently did a short demo with first trapping hrtimer_start, grabbing
&timer->state and then set a watchpoint on that address to catch changes).
>
> You could also try qemu's svm emulation, but it may be a little slow,
> and probably hasn't been well tested in these areas.
>
Yeah, could be a supplemental test.
Jan
--
Siemens AG, Corporate Technology, CT SE 26
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-12-08 9:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 11:43 [PATCH 0/5] KVM: Improved guest debugging / debug register emulation Jan Kiszka
2008-11-27 11:43 ` [PATCH 1/5] VMX: Support for injecting software exceptions Jan Kiszka
2008-11-27 11:43 ` [PATCH 4/5] KVM: x86: Virtualize debug registers Jan Kiszka
2008-11-27 11:43 ` [PATCH 2/5] KVM: New guest debug interface Jan Kiszka
2008-12-07 9:55 ` Avi Kivity
2008-12-08 9:13 ` Jan Kiszka
2008-12-08 9:34 ` Avi Kivity
2008-12-08 9:42 ` Jan Kiszka [this message]
2008-12-08 13:47 ` Jan Kiszka
2008-12-08 14:57 ` Avi Kivity
2008-12-08 15:17 ` Jan Kiszka
2008-12-10 8:48 ` Avi Kivity
2008-11-27 11:43 ` [PATCH 3/5] KVM: VMX: Ensure interruptibility when single-stepping Jan Kiszka
2008-12-07 10:05 ` Avi Kivity
2008-12-08 9:17 ` Jan Kiszka
2008-12-11 19:15 ` [PATCH] KVM: VMX: Allow single-stepping when interruptible Jan Kiszka
2008-11-27 11:43 ` [PATCH 5/5] KVM: x86: Wire-up hardware breakpoints for guest debugging Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 9:15 [PATCH 0/5] KVM: Fix and improve guest debugging and x86 debug registers Jan Kiszka
2008-10-06 9:15 ` [PATCH 2/5] KVM: New guest debug interface Jan Kiszka
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=493CEC0A.7000505@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=joerg.roedel@amd.com \
--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.