From: Thomas Gleixner <tglx@linutronix.de>
To: psodagud@codeaurora.org
Cc: Elliot Berman <eberman@codeaurora.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Trilok Soni <tsoni@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: Mon, 26 Oct 2020 20:04:25 +0100 [thread overview]
Message-ID: <8736204xmu.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <a6d7f84679240fcf580520230a88c058@codeaurora.org>
On Mon, Oct 26 2020 at 10:08, psodagud wrote:
> Based on my understanding with maxcpus option provides, maximum no of
> CPUs are brough up during the device boot up. There is a different case,
> in which we want to restrict which CPUs to be brough up.
Again: What for? Why?
> On a system with 8 cpus, if we set maxcpus as 3, cpu0, cpu1, and cpu2
> are brough up during the bootup. For example, if we want to bring
> core0, core3 and core4 current maxcpu(as 3) setting would not help us.
> On some platform we want the flexibility on which CPUs to bring up
> during the device bootup. bootcpus command line is helping to bring
> specific CPUs and these patches are working downstream.
A lot of patches work downstream by some definition of work. But that
does not make an argument to bring them upstream.
Thanks,
tglx
next prev parent reply other threads:[~2020-10-26 19:13 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
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 [this message]
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=8736204xmu.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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=peterz@infradead.org \
--cc=psodagud@codeaurora.org \
--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