From: Peter Zijlstra <peterz@infradead.org>
To: Elliot Berman <eberman@codeaurora.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Trilok Soni <tsoni@codeaurora.org>,
Prasad Sodagudi <psodagud@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] smp: Add bootcpus parameter to boot subset of CPUs
Date: Fri, 23 Oct 2020 09:45:42 +0200 [thread overview]
Message-ID: <20201023074542.GN2611@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1603404243-5536-1-git-send-email-eberman@codeaurora.org>
On Thu, Oct 22, 2020 at 03:04:03PM -0700, Elliot Berman wrote:
> In a heterogeneous multiprocessor system, specifying the 'maxcpus'
> parameter on kernel command line does not provide sufficient control
> over which CPUs are brought online at kernel boot time, since CPUs may
> have nonuniform performance characteristics. Thus, add bootcpus kernel
> parameter to control which CPUs should be brought online during kernel
> boot. When both maxcpus and bootcpus is set, the more restrictive of the
> two are booted.
Why would one wish to do so? Having the ability for abilities sake is no
good.
next prev parent reply other threads:[~2020-10-23 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 22:04 [PATCH] smp: Add bootcpus parameter to boot subset of CPUs Elliot Berman
2020-10-23 7:45 ` Peter Zijlstra [this message]
2020-10-23 21:59 ` Thomas Gleixner
2020-10-26 17:08 ` psodagud
2020-10-26 17:12 ` Peter Zijlstra
2020-10-27 17:06 ` Elliot Berman
2020-10-28 14:55 ` Qais Yousef
2020-10-28 15:15 ` Sudeep Holla
2020-10-29 21:37 ` Elliot Berman
2020-10-30 17:45 ` Sudeep Holla
2020-11-03 22:10 ` Thomas Gleixner
2020-10-26 19:04 ` Thomas Gleixner
2020-10-25 13:06 ` Qais Yousef
2020-10-28 15:55 ` Sudeep Holla
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=20201023074542.GN2611@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=corbet@lwn.net \
--cc=eberman@codeaurora.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=psodagud@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=tsoni@codeaurora.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