From: "Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
To: Bernhard Walle <bwalle@suse.de>
Cc: Jay Lan <jlan@sgi.com>, Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH] [makedumpfile] Implement memory regions on IA64
Date: Wed, 16 May 2007 20:20:00 +0900 [thread overview]
Message-ID: <20070516202000oomichi@mail.jp.nec.com> (raw)
In-Reply-To: <20070515220845.GB823@suse.de>
Hi Bernhard,
2007/05/16 00:08:45 +0200, Bernhard Walle <bwalle@suse.de> wrote:
>Hello,
>
>* Bernhard Walle <bwalle@suse.de> [2007-05-14 23:49]:
>>
>> I'm working on support for the 4 layer pagetable.
>
>Here's my first attempt. It works with SLES 10, SP1 on a Tiger4
>machine with 16 GiB of memory. (I had still problems with a big
>SGI machine when creating the bitmap. I'm investigating this, too.)
>
>The problem is not to implement the 4 layer page table, but to
>*detect* it. crash uses the built-in configuration data in the kernel
>image, and that's what I used in my patch. If you have a better and
>still reliable method, I'm open to suggestions. :-)
Thank you for the patch.
I tested makedumpfile with your patch on linux-2.6.18 ia64,
and it output the following message and failed.
Error message:
$ makedumpfile -cd 31 -x vmlinux vmcore dumpfile
Can't read kernel cofiguration from kernel binary
makedumpfile Failed.
$
The reason was that kernel binary file didn't have "kernel_config_data"
because CONFIG_IKCONFIG was not set in my .config.
It is uncertain that "kernel_config_data" exists in a kernel binary.
I propose that makedumpfile distinguishes the page table (3L or 4L)
by checking the defined file name of pud_t.
I'm trying for the above implementation.
I will send you the patch when it is complete.
All the pud_t(s) of linux-2.6.16 - 2.6.21 are defined in the following files:
CONFIG_PGTABLE_4
include/asm-ia64/page.h
!CONFIG_PGTABLE_4
include/asm-generic/pgtable-nopud.h
Thanks
Ken'ichi Ohmichi
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-05-16 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 19:37 [PATCH] [makedumpfile] Implement memory regions on IA64 Bernhard Walle
2007-05-11 6:59 ` Ken'ichi Ohmichi
2007-05-14 18:15 ` Bernhard Walle
2007-05-14 21:49 ` Bernhard Walle
2007-05-15 22:08 ` Bernhard Walle
2007-05-16 11:20 ` Ken'ichi Ohmichi [this message]
2007-05-16 11:26 ` Bernhard Walle
2007-05-21 9:32 ` Ken'ichi Ohmichi
2007-05-21 9:54 ` Bernhard Walle
-- strict thread matches above, loose matches on Subject: below --
2007-04-27 10:31 tachibana
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=20070516202000oomichi@mail.jp.nec.com \
--to=oomichi@mxs.nes.nec.co.jp \
--cc=bwalle@suse.de \
--cc=jlan@sgi.com \
--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