From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Hari Bathini <hbathini@linux.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Vasant Hegde <hegdevasant@linux.ibm.com>,
stable@vger.kernel.org,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>
Subject: Re: [PATCH v3 1/2] powerpc/fadump: use static allocation for reserved memory ranges
Date: Wed, 6 May 2020 12:51:03 +1000 (AEST) [thread overview]
Message-ID: <49H1Lc0HT8z9sRf@ozlabs.org> (raw)
In-Reply-To: <158737294432.26700.4830263187856221314.stgit@hbathini.in.ibm.com>
On Mon, 2020-04-20 at 08:56:09 UTC, Hari Bathini wrote:
> At times, memory ranges have to be looked up during early boot, when
> kernel couldn't be initialized for dynamic memory allocation. In fact,
> reserved-ranges look up is needed during FADump memory reservation.
> Without accounting for reserved-ranges in reserving memory for FADump,
> MPIPL boot fails with memory corruption issues. So, extend memory
> ranges handling to support static allocation and populate reserved
> memory ranges during early boot.
>
> Fixes: dda9dbfeeb7a ("powerpc/fadump: consider reserved ranges while releasing memory")
> Cc: stable@vger.kernel.org
> Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
> Reviewed-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/02c04e374e176ae3a3f64a682f80702f8d2fb65d
cheers
prev parent reply other threads:[~2020-05-06 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 8:56 [PATCH v3 1/2] powerpc/fadump: use static allocation for reserved memory ranges Hari Bathini
2020-04-20 8:56 ` [PATCH v3 2/2] powerpc/fadump: consider reserved ranges while reserving memory Hari Bathini
2020-05-06 2:51 ` 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=49H1Lc0HT8z9sRf@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=hbathini@linux.ibm.com \
--cc=hegdevasant@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=sourabhjain@linux.ibm.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).