From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arun Sharma <arun.sharma@intel.com>
Subject: [PATCH] show-regs.patch
Date: Fri, 27 May 2005 12:38:09 -0700
Message-ID: <20050527193809.GA13803@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

[ I know this will break non x86 archs, but something like this would be nice
  to figure out why a domain has crashed. May be we can #ifdef CONFIG_X86 for 
  now? ]

Show registers after a domain crash

Signed-off-by: Arun Sharma <arun.sharma@intel.com>

--- 1.187/xen/common/domain.c	2005-05-18 06:14:33 -07:00
+++ edited/xen/common/domain.c	2005-05-26 12:00:10 -07:00
@@ -127,6 +127,7 @@
         panic("Domain 0 crashed!\n");
     }
 
+    show_registers(guest_cpu_user_regs());
     set_bit(_DOMF_crashed, &d->domain_flags);
 
     send_guest_virq(dom0->exec_domain[0], VIRQ_DOM_EXC);