From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>,
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [v2, 1/2] powerpc/fadump: reserve memory at an offset closer to bottom of RAM
Date: Mon, 3 Apr 2017 20:13:20 +1000 (AEST) [thread overview]
Message-ID: <3vxSc029vlz9s86@ozlabs.org> (raw)
In-Reply-To: <148969794004.4130.14805754334064000704.stgit@hbathini.in.ibm.com>
On Thu, 2017-03-16 at 21:05:26 UTC, Hari Bathini wrote:
> Currently, the area to preserve boot memory is reserved at the top of
> RAM. This leaves fadump vulnerable to memory hot-remove operations. As
> memory for fadump has to be reserved early in the boot process, fadump
> can't be registered after a memory hot-remove operation. Though this
> problem can't be eleminated completely, the impact can be minimized by
> reserving memory at an offset closer to bottom of the RAM. The offset
> for fadump memory reservation can be any value greater than fadump boot
> memory size.
>
> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f6e6bedb773118713a8eb3736a4c99
cheers
prev parent reply other threads:[~2017-04-03 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 21:05 [PATCH v2 1/2] powerpc/fadump: reserve memory at an offset closer to bottom of RAM Hari Bathini
2017-03-16 21:05 ` [PATCH v2 2/2] powerpc/fadump: update fadump documentation Hari Bathini
2017-04-03 10:13 ` Michael Ellerman [this message]
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=3vxSc029vlz9s86@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).