From: Ryan Roberts <ryan.roberts@arm.com>
To: Dev Jain <dev.jain@arm.com>,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mark.rutland@arm.com,
suzuki.poulose@arm.com, broonie@kernel.org, James.Morse@arm.com,
Anshuman.Khandual@arm.com
Subject: Re: [PATCH] Documentation: Add ARM64 for reserving ZONE_MOVABLE
Date: Fri, 7 Jun 2024 12:34:42 +0100 [thread overview]
Message-ID: <8c3db3d5-8ddc-427c-8db2-980b14afb258@arm.com> (raw)
In-Reply-To: <20240604052856.546183-1-dev.jain@arm.com>
On 04/06/2024 06:28, Dev Jain wrote:
> kernelcore and movablecore kernel command line works for ARM64. Update
> the Documentation to reflect the same.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index b600df82669d..7282d6057e32 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -2544,7 +2544,7 @@
>
> keepinitrd [HW,ARM] See retain_initrd.
>
> - kernelcore= [KNL,X86,IA-64,PPC,EARLY]
> + kernelcore= [KNL,X86,IA-64,PPC,ARM64,EARLY]
Given these are both arch-agnostic parameters, wouldn't the correct change be to
remove all the arch-specific labels, i.e. [KNL,EARLY]? In fact, wasn't IA-64
removed from the kernel?
> Format: nn[KMGTPE] | nn% | "mirror"
> This parameter specifies the amount of memory usable by
> the kernel for non-movable allocations. The requested
> @@ -3612,7 +3612,7 @@
> mousedev.yres= [MOUSE] Vertical screen resolution, used for devices
> reporting absolute coordinates, such as tablets
>
> - movablecore= [KNL,X86,IA-64,PPC,EARLY]
> + movablecore= [KNL,X86,IA-64,PPC,ARM64,EARLY]
> Format: nn[KMGTPE] | nn%
> This parameter is the complement to kernelcore=, it
> specifies the amount of memory used for migratable
next prev parent reply other threads:[~2024-06-07 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 5:28 Dev Jain
2024-06-07 11:34 ` Ryan Roberts [this message]
2024-06-11 10:16 ` Dev 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=8c3db3d5-8ddc-427c-8db2-980b14afb258@arm.com \
--to=ryan.roberts@arm.com \
--cc=Anshuman.Khandual@arm.com \
--cc=James.Morse@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dev.jain@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@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
all inboxes | Powered by JetHome®