From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: Kdump for ARM (vmcore generation problem)
Date: Mon, 20 Aug 2007 13:53:59 +0200 [thread overview]
Message-ID: <20070820115359.GA21033@suse.de> (raw)
In-Reply-To: <46C98029.2000800@samsung.com>
* Indraneel <indraneel.m@samsung.com> [2007-08-20 13:51]:
> Hi Vivek/Bernhard,
>
> Vivek Goyal wrote:
> > On Tue, Aug 14, 2007 at 06:41:54PM +0530, Indraneel wrote:
> >> Hi,
> >> I'm trying to make Kdump work for ARM. Till now i've managed to get the
> >> /dev/oldmem interface working for taking dumps. Now i want to get the
> >> /proc/vmcore interface working.
> >> I'm unclear how to generate the elfcore headers required by routines in
> >> vmcore.c.
> >>
> >
> > Hi Indraneel,
> >
> > kexec-tools in user space generates those headers. Have a loot at
> > kexec-tools code.
>
> Thanks for the lead. I'm looking into kexec-tools and trying to do
> changes for ARM. I'm unable to interpret one of the comments in
> kexec/crashdump-elf.c which says,
> " The separate PT_LOAD program header is required either because the
> kernel is mapped at a different location than the rest of the
> physical memory or because we need to support relocatable kernels.
> Or both as on x86_64. "
>
> Can you please provide some more clarification for this so that i can
> figure out whether a separate PT_LOAD header is required for ARM
> architecture as well (esp. the "kernel mapped to diff. loc. part of the
> comment").
Is the ARM kernel relocatable? If no, then you don't need this.
Thanks,
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2007-08-20 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 13:11 Kdump for ARM (vmcore generation problem) Indraneel
2007-08-14 19:18 ` Bernhard Walle
2007-08-16 3:02 ` Vivek Goyal
2007-08-20 11:51 ` Indraneel
2007-08-20 11:53 ` Bernhard Walle [this message]
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=20070820115359.GA21033@suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox