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

["Kazuo Moriwaka" <moriwaka@xxxxxxxxxxxxx>]

HI, Akio,

On 4/25/06, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx> wrote:
> Could you explain usage of your tool?

I'm sorry for lack of description.
Its usage is:
  ./dom0cut_x86_32.py -oOutputFile -dDumpFile -xXenSymsFile -vVmlinuxFile -telf

Argument -t 's filetype is input dumpfile's type.

and it shows some help:
   ./dom0cut_x86_32.py --help

> For using your tool, do I need xen-syms, vmlinux(with debug option),
> and so on?

Yes, and internally, it calls readelf and nm to fetch ELF sections and
some info.
# now this script doesn't use vmlinux debug info yet.

> Can this tool extract only dom0 from coredump file?
Yes, now it extract only dom0.

> Can this tool also extract xen or domU?

Not yet. But I think to extend the script to extract domU is not so difficult.

To support domU:
- In dom0cut_x86_32.py, dom0extract() calls XenImage.get_dom0p() to
get *dom0 now.
  It should be replaced with some function like
XenImage.get_domainp(id) to extract
  domU image.

- kdump saves dom0's latest CPU register info ELF core's PT_NOTE,
  so dom0 needs some special treatment about register.

For xen, I'm not clear how to set up suitable context information
for dump file.

regards,
--
Kazuo Moriwaka

> Best Regards,
>
> Akio Takebe
>
> >I forgot attach my scripts and readme.
> >
> >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
> >
> >-------------------------------text/plain-------------------------------
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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