 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386
| To: | "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386 |
| From: | "Kazuo Moriwaka" <moriwaka@xxxxxxxxxxxxx> |
| Date: | Mon, 24 Apr 2006 10:16:34 +0900 |
| Cc: | Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, Magnus Damm <magnus@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, horms-home@xxxxxxxxxxxx |
| Delivery-date: | Sun, 23 Apr 2006 18:16:53 -0700 |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hq4YABgUUwJ83FhcfPss6+mif1gzqkJTs/qLGv0Y3RWoFWVuNxmXVwUJBx9CXEsfaA28u44KVzy1qMrY5vDNQQEr7DjHijtbM4KcdPtXNBgnniZ4FS9VXvvrYKAIiTo8Bv/RDDTfBNjEcCptcxs5h0KMR7WkXyOYzk7zRuuAbI8= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <A95E2296287EAD4EB592B5DEEFCE0E9D4BA3F4@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <A95E2296287EAD4EB592B5DEEFCE0E9D4BA3F4@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Hi, On 4/24/06, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote: > > When a panic occurs, Linux kexec jumps into the preloaded > > kdump kernel (if any). This kernel then reinitiases the > > hardware, using its own device drivers and uses these to > > write out the dump to disk. ISTR that the dump format is > > currently ELF, although I remember some talk on the Fastboot > > ML about adding some extra headers to make OS debugging easier. > > Is Xen and the dom0 kernel dumped as as separate ELF cores? I'm working on clipping domain image from whole-machine dump for x86_32 now. Now my prototype reads ELF core and write dom0 image. todo: - Output format is not ELF core yet. Xen domain core image format(works with gdbserverxen). - register information is not work well. -- Kazuo Moriwaka _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386, Akio Takebe |
|---|---|
| Next by Date: | Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386, Kazuo Moriwaka |
| Previous by Thread: | Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386, Mark Williamson |
| Next by Thread: | Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386, Kazuo Moriwaka |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
