[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: domain_pause_for_debugger not pausing multiple vcpus
- To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Kip Macy <kip.macy@xxxxxxxxx>
- Date: Sat, 3 Dec 2005 23:46:25 -0600
- Delivery-date: Sun, 04 Dec 2005 05:47:23 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=NOgYmg70UCXFsWwdkF+HwyJ8KouuJUPjRUWKGEq3rNwT9z9cmkAaWnUdnSj0G2hUh4U2t1woeNxWdRFfK6eZhOHUmQUKUxLRd6+KkS9v7czVytGsECd6jhrsMs56+a3ISzI9ZTRguUmoSIMIGwK7qQ0XIhEoJikrs4zTP8DZkbI=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Never mind. I wasn't setting the current_inferior to the VCPU that hit
the breakpoint, thus causing the eip to not be decremented. At least on
a uniprocessor, debugging an MP guest works correctly now.
Sorry for the noise.
-Kip
On 12/3/05, Kip Macy <kip.macy@xxxxxxxxx> wrote:
Debugging an MP guest doesn't work. It appears that if a vcpu other than 0 hits an int3 it doesn't get paused.
If the comment in domain_pause_for_debugger is correct (below), this
function is completely inappropriate for breakpoint debugging.
NOTE: Thise does not synchronously pause the domain. The debugger
must issue a PAUSEDOMAIN command to ensure that all execution
has ceased and guest state is committed to memory.
What is the correct way to synchronously deschedule a domain? Replacing
vcpu_sleep_nosync with vcpu_sleep_sync causes dom0 to lock up when
hitting a breakpoint.
Thanks.
-Kip
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
