From: ebiederm@xmission.com (Eric W. Biederman)
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "Zou, Nanhai" <nanhai.zou@intel.com>,
khalid_aziz@hp.com, linux-kernel@vger.kernel.org,
fastboot@lists.osdl.org, linux-ia64@vger.kernel.org
Subject: Re: [Fastboot] [PATCH] kexec on ia64
Date: Wed, 05 Apr 2006 02:49:49 +0000 [thread overview]
Message-ID: <m1vetoivn6.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060405101243.e3e4f772.kamezawa.hiroyu@jp.fujitsu.com> (KAMEZAWA Hiroyuki's message of "Wed, 5 Apr 2006 10:12:43 +0900")
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> Hi, I have a question about kexec/kdump.
>
> How does kdump know memory layout (of old kernel) now ?
>
> I'm working for memory hotplug. When memory is hot-added, memory layout changes.
> But I think there is no code to manage memory layout information of added
> memory.
It is passed from one kernel to another, and it is memorized when you load
the crash dump kernel. If your memory layout changes you need to reload
the crash dump kernel from user space with the appropriate hotplug script.
Unless this happens often it shouldn't be a problem.
And yes this does leave a small race during which kexec on panic won't
work.
Eric
next prev parent reply other threads:[~2006-04-05 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 20:41 [Fastboot] [PATCH] kexec on ia64 Khalid Aziz
2004-11-16 3:46 ` Khalid Aziz
2006-04-05 0:36 ` Zou, Nanhai
[not found] ` <20060405101243.e3e4f772.kamezawa.hiroyu@jp.fujitsu.com>
2006-04-05 2:49 ` Eric W. Biederman [this message]
2006-04-05 4:31 ` KAMEZAWA Hiroyuki
2006-04-05 1:13 ` Zou, Nanhai
2006-04-05 1:27 ` KAMEZAWA Hiroyuki
2006-04-05 1:34 ` Zou, Nanhai
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:20 Khalid Aziz
2006-04-04 18:13 ` [Fastboot] " Eric W. Biederman
2006-04-05 16:34 ` Khalid Aziz
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=m1vetoivn6.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=khalid_aziz@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox