From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Mike Rapoport <rppt@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Mike Rapoport <rppt@linux.ibm.com>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
<linux-doc@vger.kernel.org>, <linux-mips@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docs/kernel-parameters: update description of mem=
Date: Wed, 9 Mar 2022 19:20:42 +0300 [thread overview]
Message-ID: <d3679148-598e-4b58-96be-e3ab255ab8d9@omp.ru> (raw)
In-Reply-To: <20220309122446.1118738-1-rppt@kernel.org>
On 3/9/22 3:24 PM, Mike Rapoport wrote:
> From: Mike Rapoport <rppt@linux.ibm.com>
>
> The existing description of mem= does not cover all the cases and
> differences between how architectures treat it.
>
> Extend the description to match the code.
>
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
>
> This is in a way a followup for the discussion of mem= usage on MIPS:
>
> https://lore.kernel.org/all/1646461289-31992-1-git-send-email-yangtiezhu@loongson.cn
>
> .../admin-guide/kernel-parameters.txt | 20 +++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index f5a27f067db9..f3597841a031 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -2834,6 +2834,15 @@
> 2 when the kernel is not able to see the whole system memory;
> 3 memory that lies after 'mem=' boundary is excluded from
> the hypervisor, then assigned to KVM guests.
> + 4 to limit the memory available for kdump kernel.
> +
> + [ARC,MICROBLAZE] - the limit applies only to low memory,
> + high memory is not affected.
> +
> + [ARM64] - only limits memory covered by the linear
> + mapping. The NOMAP regions are not affected.
> +
> + [HEXAGON] - must be use
Used?
> to set the memory size, there is
What? :-)
[...]
MBR, Sergey
prev parent reply other threads:[~2022-03-09 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:24 [PATCH] docs/kernel-parameters: update description of mem= Mike Rapoport
2022-03-09 16:05 ` Randy Dunlap
2022-03-09 16:56 ` Mike Rapoport
2022-03-09 16:20 ` Sergey Shtylyov [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=d3679148-598e-4b58-96be-e3ab255ab8d9@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=macro@orcam.me.uk \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=tsbogend@alpha.franken.de \
--cc=yangtiezhu@loongson.cn \
/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).