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/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: [PATCH]: kexec: framework and i386
From: "Kazuo Moriwaka" <moriwaka@xxxxxxxxxxxxx>
Date: Fri, 19 May 2006 20:21:42 +0900
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Magnus Damm <magnus@xxxxxxxxxxxxx>, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, horms-home@xxxxxxxxxxxx
Delivery-date: Fri, 19 May 2006 04:22:10 -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:references:x-google-sender-auth; b=hjS3ZItBkSJLVAXJdVg3kwekESId5DjoGyeM3L4N1gVhxqJKU6plP1kIYgkgU7iyEqUsshFVH+ehqI6tUkq1Fihn+kXXyFxGZMEqRadh3lwRefoLW+rSHDrsMoJ4vvCdsHGcvCINFf//wF2oksnycxzeFjjejgKjFONOuOP/+Cg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <b294a32a0605092349p7e17d043k68f3b4466407323@xxxxxxxxxxxxxx>
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> <b294a32a0604231816i1be50586k9c788bf134f50b59@xxxxxxxxxxxxxx> <b294a32a0605092349p7e17d043k68f3b4466407323@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I update dom0cut script to extract dom0 in both Xen Core and ELF Core format.
With ELF Core, you can use gdb without gdbserver-xen.

typical usage is:
$ ./dom0cut.py -telf -f -dvmcore -odom0core -xxen-syms -vvmlinux-2.6.16
$ gdb vmlinux-2.6.16 dom0core
$ ./dom0cut.py -txen -f -dvmcore -odom0core -xxen-syms -vvmlinux-2.6.16
$ gdbserver-xen localhost:9999 --file dom0core

To make ELF headers, It use libelf
and SWIG (http://www.swig.org/).

I attach the patch and libelf wrapper.

- SMP support.
- other architecture support.

On 5/10/06, Kazuo Moriwaka <moriwaka@xxxxxxxxxxxxx> wrote:

I'll send a patch for dom0 image extract (from kdump) script.

Update is..
- get register values in dom0 context from kdump's ELF Core PT_NOTE header.
- get cr3 register value in context info from vcpu.
- now you can look vmlinux symbols from gdbserver-xen.

- It support only single processor now.
- ELF Core output.

On 4/24/06, Kazuo Moriwaka <moriwaka@xxxxxxxxxxxxx> wrote:
> 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

Kazuo Moriwaka

Attachment: dumpread.diff
Description: Text Data

Attachment: libelf-0.1.0.tar.gz
Description: GNU Zip compressed data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>