From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Zytaruk, Kelly" <Kelly.Zytaruk@amd.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: dumping Xen stack
Date: Mon, 9 May 2016 18:13:41 +0100 [thread overview]
Message-ID: <5730C545.4010808@citrix.com> (raw)
In-Reply-To: <CY1PR12MB026258CD5AE598C49F9BE5C9FE700@CY1PR12MB0262.namprd12.prod.outlook.com>
On 09/05/16 18:11, Zytaruk, Kelly wrote:
>
>> -----Original Message-----
>> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
>> Sent: Monday, May 09, 2016 12:40 PM
>> To: Zytaruk, Kelly; xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] dumping Xen stack
>>
>> On 09/05/16 17:37, Zytaruk, Kelly wrote:
>>> Does Xen have an equivalent function to the Linux dump_stack() function?
>>>
>>> I am hitting a panic followed by a reboot and would like to find out where I am
>> coming from.
>>
>> At the point of a crash, the stack should be printed on the console.
> The only thing I am seeing on the console is the panic message followed by the system will reboot in 5 sec.
Ah - plain panic()s don't automatically dump register/stack information.
>> Alternatively, show_execution_state() at any point should dump the Xen
>> register/stack.
> I looked up show_execution_state() and show_trace() and they both require a pointer to registers.
> I am hitting a panic during boot in queue_invalidate_wait() in .../drivers/passthrough/vtd/qinval.c . I am not sure how to get the register pointer from here.
Oops sorry - I meant dump_execution_state() which takes no parameters.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-09 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:37 dumping Xen stack Zytaruk, Kelly
2016-05-09 16:39 ` Andrew Cooper
2016-05-09 17:11 ` Zytaruk, Kelly
2016-05-09 17:13 ` Andrew Cooper [this message]
2016-05-09 17:58 ` Zytaruk, Kelly
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=5730C545.4010808@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Kelly.Zytaruk@amd.com \
--cc=xen-devel@lists.xen.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.