From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Baoquan he <bhe@redhat.com>, Jiri Bohac <jbohac@suse.cz>,
Hari Bathini <hbathini@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Shivang Upadhyay <shivangu@linux.ibm.com>
Subject: Re: [PATCH v4] powerpc/kdump: Add support for crashkernel CMA reservation
Date: Fri, 31 Oct 2025 16:48:16 +0530 [thread overview]
Message-ID: <87jz0b7213.ritesh.list@gmail.com> (raw)
In-Reply-To: <87ldkr72sq.ritesh.list@gmail.com>
Ritesh Harjani (IBM) <ritesh.list@gmail.com> writes:
>>>
>>> I am not much familiar with the crash kernel workings but was curious
>>> about the following query related to this patch:
>>>
>>> As I understand this patch allows for the remaining crash kernel
>>> memory to come from CMA region. But do we limit the CMA region to be lower
>>> than 4G?
>>
>> No we are not and we don't need to.
>>
>>> Is this patch dependent over your other patch series [1] which
>>> supports high crashkernel reservation?
>>>
>>> [1]: https://lore.kernel.org/linuxppc-dev/20251027151338.819957-1-sourabhjain@linux.ibm.com/
>>
>> No, this is an independent patch.
>>
>
> Say, if we are in Hash mode and if the CMA reservations have come from
> higher addresses. Will that work with kdump kernel when it boots with Hash
> mmu? Because memory region beyond RMA is not accessible in Hash correct?
>
Oh sorry my bad! I think I got the answer to above question now.
So this feature allows us to reserve the "extra memory" using CMA which
is mainly used to serve the kdump kernel's memory allocation requests.
So we will have two memory reservations i.e.
crashkernel=64M,crashkernel=1G,cma.
So the second 1G cma reservation is mainly to serve the kdump kernel's
memory allocation requests to avoid the ooms. And this will only be
required once the MMU is initialized, so we don't have those RMA
restrictions which are only during early init time (before Hash is
initialized).
-ritesh
next prev parent reply other threads:[~2025-10-31 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:09 [PATCH v4] powerpc/kdump: Add support for crashkernel CMA reservation Sourabh Jain
2025-10-31 3:57 ` Ritesh Harjani
2025-10-31 6:06 ` Sourabh Jain
2025-10-31 11:01 ` Ritesh Harjani
2025-10-31 11:18 ` Ritesh Harjani [this message]
2025-11-03 4:06 ` Sourabh Jain
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=87jz0b7213.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=jbohac@suse.cz \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=shivangu@linux.ibm.com \
--cc=sourabhjain@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.