From: Andrew Morton <akpm@linux-foundation•org>
To: Amerigo Wang <amwang@redhat•com>
Cc: fenghua.yu@intel•com, nhorman@redhat•com, tony.luck@intel•com,
linux-ia64@vger•kernel.org, amwang@redhat•com,
linux-kernel@vger•kernel.org, linuxppc-dev@ozlabs•org,
andi@firstfloor•org, ebiederm@xmission•com, mingo@elte•hu,
bernhard.walle@gmx•de, kamezawa.hiroyu@jp•fujitsu.com
Subject: Re: [Patch 0/8] V4 Implement crashkernel=auto
Date: Fri, 21 Aug 2009 17:06:15 -0700 [thread overview]
Message-ID: <20090821170615.1ea4a4f4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090821065637.4855.32234.sendpatchset@localhost.localdomain>
(cc linuxppc-dev@ozlabs•org)
On Fri, 21 Aug 2009 02:54:12 -0400
Amerigo Wang <amwang@redhat•com> wrote:
> This series of patch implements automatically reserved memory for crashkernel,
> by introducing a new boot option "crashkernel=auto". This idea is from Neil.
>
> In case of breaking user-space applications, it modifies this boot option after
> it decides how much memory should be reserved.
>
> On different arch, the threshold and reserved memory size is different. Please
> refer patch 8/8 which contains an update for the documentation.
>
> Patch 1/8 implements shrinking reserved memory at run-time, which is useful
> when more than enough memory is reserved automatically.
>
> Note: This patchset was only tested on x86_64 with differernt memory sizes.
I'd prefer that this change had been runtime tested on ia64 and powerpc
and has had some quality review from relevant developers of those
architectures.
Looking at the cc's, I'm not sure that the powerpc guys even know about
this work?
next parent reply other threads:[~2009-08-22 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090821065637.4855.32234.sendpatchset@localhost.localdomain>
2009-08-22 0:06 ` Andrew Morton [this message]
2009-08-24 1:34 ` [Patch 0/8] V4 Implement crashkernel=auto Amerigo Wang
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=20090821170615.1ea4a4f4.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=amwang@redhat$(echo .)com \
--cc=andi@firstfloor$(echo .)org \
--cc=bernhard.walle@gmx$(echo .)de \
--cc=ebiederm@xmission$(echo .)com \
--cc=fenghua.yu@intel$(echo .)com \
--cc=kamezawa.hiroyu@jp$(echo .)fujitsu.com \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mingo@elte$(echo .)hu \
--cc=nhorman@redhat$(echo .)com \
--cc=tony.luck@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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