All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Kazuo Moriwaka <moriwaka@valinux.co.jp>,
	Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Akio Takebe <takebe_akio@jp.fujitsu.com>,
	Magnus Damm <magnus@valinux.co.jp>,
	xen-devel@lists.xensource.com,
	Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: Re: [PATCH]: kexec: framework and i386
Date: Tue, 25 Apr 2006 10:15:24 +0900	[thread overview]
Message-ID: <6AC66805BACE46takebe_akio@jp.fujitsu.com> (raw)
In-Reply-To: <b294a32a0604231830j4e4de03nd011a929dc09eac@mail.gmail.com>

Hi, Kazuo

Good work!
Could you explain usage of your tool?
For using your tool, do I need xen-syms, vmlinux(with debug option), 
and so on?
Can this tool extract only dom0 from coredump file?
Can this tool also extract xen or domU?

Best Regards,

Akio Takebe

>I forgot attach my scripts and readme.
>
>On 4/24/06, Kazuo Moriwaka <moriwaka@valinux.co.jp> wrote:
>> Hi,
>>
>> On 4/24/06, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> 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@lists.xensource.com
>http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-04-25  1:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-23 22:03 Re: [PATCH]: kexec: framework and i386 Ian Pratt
2006-04-23 22:47 ` Mark Williamson
2006-04-24  1:16 ` Kazuo Moriwaka
2006-04-24  1:30   ` Kazuo Moriwaka
2006-04-25  1:15     ` Akio Takebe [this message]
2006-04-25  2:34       ` Kazuo Moriwaka
2006-05-10  6:49   ` Kazuo Moriwaka
2006-05-10  6:50     ` Kazuo Moriwaka
2006-05-19 11:21     ` Kazuo Moriwaka
  -- strict thread matches above, loose matches on Subject: below --
2006-04-23 14:33 Ian Pratt
2006-04-23 14:53 ` Mark Williamson
2006-04-23 15:53   ` Hirokazu Takahashi
2006-04-07  7:42 Horms
2006-04-12  9:12 ` Horms
2006-04-17  6:06   ` Horms
2006-04-21  6:10     ` Akio Takebe
2006-04-21  6:55       ` horms-home
2006-04-21  7:53         ` Akio Takebe
2006-04-23 14:45       ` Mark Williamson
2006-04-24  1:10         ` Akio Takebe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6AC66805BACE46takebe_akio@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=magnus@valinux.co.jp \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=moriwaka@valinux.co.jp \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.