From: Bernhard Walle <bwalle@suse.de>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: Jay Lan <jlan@sgi.com>, Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH] [makedumpfile] Implement memory regions on IA64
Date: Mon, 14 May 2007 20:15:21 +0200 [thread overview]
Message-ID: <20070514181521.GA1748@suse.de> (raw)
In-Reply-To: <20070511155950oomichi@mail.jp.nec.com>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
Hi,
sorry for the late reply, but I was out of office last week.
* Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp> [2007-05-11 08:59]:
> 2007/04/26 21:37:25 +0200, Bernhard Walle <bwalle@suse.de> wrote:
> >This patch fixes an error in vaddr_to_offset_ia64() which happened on
> >a SGI machine here while retrieving the utsname from the kernel dump
> >image. It implements memory region support for IA64.
>
> For ia64 DISCONTIGMEM support, I added the translation (virtual address
> to physical address) by using layer 3 paging into your patch.
> I created 2 attached patches for ia64 DISCONTIGMEM support.
>
> I confirmed makedumpfile with these patches can run on linux-2.6.18 kernel
> (made of RHEL5 kernel by changing configs from SPARSEMEM to DISCONTIGMEM).
> Could you please test them on SLES10 ?
it doesn't work here. The config file is generated, but at runtime I
get a SEGV which is caused by a endless recusion of ia64_vtop() while
resolving the utsname.
I'm looking into this ...
> BTW, the patches don't run on stock linux-2.6.20 w/DISCONTIGMEM
> (it works with stock linux-2.6.20 w/SPARSEMEM)
> I am trying to resolve the problem and if you have any idea about
> kernel changes between 2.6.18-20, please let me know.
Sorry, no.
Thanks,
Bernhard
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-05-14 18:15 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 [this message]
2007-05-14 21:49 ` Bernhard Walle
2007-05-15 22:08 ` Bernhard Walle
2007-05-16 11:20 ` Ken'ichi Ohmichi
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=20070514181521.GA1748@suse.de \
--to=bwalle@suse.de \
--cc=jlan@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.nes.nec.co.jp \
/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