From: Indraneel <indraneel.m@samsung.com>
To: vgoyal@in.ibm.com
Cc: kexec@lists.infradead.org
Subject: Re: Kdump for ARM (vmcore generation problem)
Date: Mon, 20 Aug 2007 17:21:05 +0530 [thread overview]
Message-ID: <46C98029.2000800@samsung.com> (raw)
In-Reply-To: <20070816030251.GA20860@in.ibm.com>
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").
TIA,
Indro
>
> Thanks
> Vivek
>
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-08-20 11:43 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 [this message]
2007-08-20 11:53 ` Bernhard Walle
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=46C98029.2000800@samsung.com \
--to=indraneel.m@samsung.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@in.ibm.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.