linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
	Avnish Chouhan <avnish@linux.ibm.com>,
	Brian King <brking@linux.ibm.com>,
	Hari Bathini <hbathini@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>
Subject: [PATCH 0/2] powerpc/fadump: fix additional parameter for HASH MMU
Date: Mon, 20 Jan 2025 23:04:58 +0530	[thread overview]
Message-ID: <20250120173501.1147236-1-sourabhjain@linux.ibm.com> (raw)

Patch https://lore.kernel.org/all/20241206065545.14815-1-avnish@linux.ibm.com/
proposed the MIN RMA change to 768MB, which impacts the fadump additional
parameter feature for HASH MMU. Here’s how:

Commit 683eab94da75bc ("powerpc/fadump: setup additional parameters for
dump capture kernel") introduced the additional parameter feature in
fadump for HASH MMU with the understanding that GRUB does not use the
memory area between 640MB and 768MB for its operation.

However, the patch ("powerpc: increase MIN RMA size for CAS
negotiation") changes the MIN RMA size to 768MB, allowing GRUB to use
memory up to 768MB. This makes the fadump reservation for the additional
parameter feature for HASH MMU unreliable.

To address this, adjust the memory range for the additional parameter in
fadump for HASH MMU. This will ensure that GRUB does not overwrite the
memory reserved for fadump additional parameter in HASH MMU.

The first patch exports the MIN_RMA so that fadump can dynamically
decide the suitable memory range for the additional parameter. This will
help us avoid similar fadump changes in the future.

The second patch includes changes that actually fix the issue described
above.

Note:
This patch series is dependent on the below patch:
https://lore.kernel.org/all/20241206065545.14815-1-avnish@linux.ibm.com/

Cc: Avnish Chouhan <avnish@linux.ibm.com>
Cc: Brian King <brking@linux.ibm.com>
Cc: Hari Bathini <hbathini@linux.ibm.com>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>

Sourabh Jain (2):
  powerpc: export MIN RMA size
  powerpc/fadump: fix additional param memory reservation for HASH MMU

 arch/powerpc/include/asm/prom.h |  2 ++
 arch/powerpc/kernel/fadump.c    | 21 +++++++++++----------
 arch/powerpc/kernel/prom_init.c |  2 +-
 3 files changed, 14 insertions(+), 11 deletions(-)

-- 
2.47.1



             reply	other threads:[~2025-01-20 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 17:34 Sourabh Jain [this message]
2025-01-20 17:34 ` [PATCH 1/2] powerpc: export MIN RMA size Sourabh Jain
2025-01-20 17:35 ` [PATCH 2/2] powerpc/fadump: fix additional param memory reservation for HASH MMU Sourabh Jain
2025-01-23  6:58   ` Mahesh J Salgaonkar
2025-01-24  3:34     ` Sourabh Jain
2025-01-23  9:56   ` Hari Bathini
2025-01-23 14:24     ` Avnish Chouhan
2025-01-31 15:14       ` Hari Bathini
2025-02-04  5:28         ` Avnish Chouhan
2025-02-04  6:27           ` Hari Bathini
2025-02-04  8:37             ` Avnish Chouhan
2025-02-10  6:44               ` Hari Bathini

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=20250120173501.1147236-1-sourabhjain@linux.ibm.com \
    --to=sourabhjain@linux.ibm.com \
    --cc=avnish@linux.ibm.com \
    --cc=brking@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    /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).