From: Sudeep Holla <sudeep.holla@arm.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andreas Schwab <schwab@suse.de>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Johan Hovold <johan@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Anup Patel <anup@brainfault.org>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 2/4] RISC-V: Implement nosmp commandline option.
Date: Thu, 25 Apr 2019 10:41:47 +0100 [thread overview]
Message-ID: <20190425094147.GA6585@e107155-lin> (raw)
In-Reply-To: <20190424214801.18880-3-atish.patra@wdc.com>
On Wed, Apr 24, 2019 at 02:47:59PM -0700, Atish Patra wrote:
> nosmp command line option sets max_cpus to zero. No secondary harts
> will boot if this is enabled. But present cpu mask will still point to
> all possible masks.
>
> Fix present cpu mask for nosmp usecase.
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
I just noticed RISC-V has CONFIG_SMP option configurable. ARM64 has
it always on and no option to disable :)
Anyways, this looks good.
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
--
Regards,
Sudeep
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-04-25 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 21:47 [PATCH v4 0/4] Miscellaneous kernel command line fixes Atish Patra
2019-04-24 21:47 ` [PATCH 1/4] RISC-V: Add RISC-V specific arch_match_cpu_phys_id Atish Patra
2019-04-24 21:47 ` [PATCH 2/4] RISC-V: Implement nosmp commandline option Atish Patra
2019-04-25 9:41 ` Sudeep Holla [this message]
2019-04-24 21:48 ` [PATCH 3/4] RISC-V: Support nr_cpus command line option Atish Patra
2019-04-25 9:59 ` Sudeep Holla
2019-04-24 21:48 ` [PATCH 4/4] RISC-V: Fix minor checkpatch issues Atish Patra
2019-04-25 8:44 ` Christoph Hellwig
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=20190425094147.GA6585@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=Damien.LeMoal@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=hch@lst.de \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@suse.de \
/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).