[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



I forget attach the patch.

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

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.

Todo:
- 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

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.