From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>, kexec@lists.infradead.org
Cc: horms@verge.net.au
Subject: Re: [PATCH] ppc64: remove rma_top limit
Date: Tue, 20 Sep 2022 10:21:28 +0530 [thread overview]
Message-ID: <b2133953-404f-7b03-7ae7-f25085e42766@linux.ibm.com> (raw)
In-Reply-To: <3ec0476b-275e-8a12-72f0-780b5e08cb1c@linux.ibm.com>
On 16/09/22 16:28, Hari Bathini wrote:
>
>
> On 15/09/22 2:12 pm, Sourabh Jain wrote:
>> Restricting kexec tool to allocate hole for kexec segments below 768MB
>> may not be relavent now since first memory block size can be 1024MB and
>> more.
>>
>> Removing rma_top restriction will give more space to find holes for
>> kexec segments and existing in-place checks make sure that kexec segment
>> allocation doesn't cross the first memory block because every kexec
>> segment
>> has to be within first memory block for kdump kernel to boot properly.
>>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>
> Yeah. The restriction seems arbitrary. Even more so since commit
> 47478ea66d43 ("kexec-tools: ppc64: fix how RMA top is deduced")
> with which kexec_load was sure to place all segments within the
> first memory block. So, the change looks good to me.
>
> Acked-by: Hari Bathini <hbathini@linux.ibm.com>
Thank you!
Sourabh Jain
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2022-09-20 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 8:42 [PATCH] ppc64: remove rma_top limit Sourabh Jain
2022-09-16 10:58 ` Hari Bathini
2022-09-20 4:51 ` Sourabh Jain [this message]
2022-09-20 7:14 ` Coiby Xu
2022-09-24 12:10 ` Simon Horman
2022-09-29 6:49 ` Sourabh Jain
2022-10-05 15:20 ` Simon Horman
2022-09-28 10:42 ` 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=b2133953-404f-7b03-7ae7-f25085e42766@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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 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.