From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: __dump_execstate() + x86's dump_exececution_state()
Date: Fri, 12 Jan 2007 17:40:12 +0000 [thread overview]
Message-ID: <C1CD787C.78D7%keir@xensource.com> (raw)
In-Reply-To: <45A7C2EA.76E4.0078.0@novell.com>
On 12/1/07 16:18, "Jan Beulich" <jbeulich@novell.com> wrote:
> I find it rather useless that due to the use of ud2 here, the context printed
> is
> always in Xen, even if what was interrupted (and hence active at the point)
> was guest code. I would want to utilize the frame
> smp_call_function_interrupt()
> sees, and am therefore wondering if it would be acceptable to add a simple
> hack to this function to pass the frame pointer as info in case the requested
> info was NULL. Or whether there are other ideas how to enhance the situation
> here.
Good point. I've now fixed it to dump *both* guest context and Xen context
always (or print that the vcpu is idling and print only Xen context).
-- Keir
prev parent reply other threads:[~2007-01-12 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-12 16:18 __dump_execstate() + x86's dump_exececution_state() Jan Beulich
2007-01-12 17:40 ` Keir Fraser [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=C1CD787C.78D7%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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.