From: Jonathan Corbet <corbet@lwn.net>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
rdunlap@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, kernel@gpiccoli.net, kernel-dev@igalia.com,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Changwoo Min <changwoo@igalia.com>
Subject: Re: [PATCH] docs: Document possible_cpus parameter
Date: Mon, 05 Feb 2024 10:21:31 -0700 [thread overview]
Message-ID: <87h6imvnc4.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240203152208.1461293-1-gpiccoli@igalia.com>
"Guilherme G. Piccoli" <gpiccoli@igalia.com> writes:
> The number of possible CPUs is set be kernel in early boot time through
> some discovery mechanisms, like ACPI in x86. We have a parameter both
> in x86 and S390 to override that - there are some cases of BIOSes exposing
> more possible CPUs than the available ones, so this parameter is a good
> testing mechanism, but for some reason wasn't mentioned so far in the
> kernel parameters guide - let's fix that.
>
> Cc: Changwoo Min <changwoo@igalia.com>
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 5 +++++
> 1 file changed, 5 insertions(+)
Applied, thanks.
jon
prev parent reply other threads:[~2024-02-05 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 15:21 [PATCH] docs: Document possible_cpus parameter Guilherme G. Piccoli
2024-02-03 17:19 ` Randy Dunlap
2024-02-05 17:21 ` Jonathan Corbet [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=87h6imvnc4.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=changwoo@igalia.com \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=gpiccoli@igalia.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).