WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-ia64-devel] Re: [Xen-devel] [Patch][0/2]implement dump_execution_st

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] Re: [Xen-devel] [Patch][0/2]implement dump_execution_state() on ia64
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Fri, 28 Mar 2008 02:22:23 +0900
Delivery-date: Thu, 27 Mar 2008 10:20:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C411843A.1E701%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C411843A.1E701%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

>On 27/3/08 16:56, "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx> wrote:
>
>>> Can you carefully explain why the interface changes are required?
>>> 
>> IA64 needs unwind infomation to show the Calltrace.
>> To make the unwind infomation, we needs switch stack and pt_regs.
>> So if possible, I want to use pt_regs at geting a interrupt.
>> 
>> I make many interface change because debug-key use IPI.
>> But I just want to use pt_regs.
>
>There is already a function which does what you want (i.e., takes a
>cpu_user_regs pointer) -- it's called show_execution_state().
>
>On x86 we implement dump_execution_state() by forcing an exception (by
>executing an invalid opcode) and dumping the calltrace from within the
>exception handler. This works because the exception handler has a
>cpu_user_regs pointer and hence can call show_execution_state(). We use the
>same trick for handling BUG() and ASSERT(). The code concerned is in
>arch/x86/traps.c:do_invalid_op().
On x86, does "xm debug-key d" make system hang?
Or it just uses the exception handler, not hangup?

Best Regards,

Akio Takebe


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel