From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>
Subject: Re: maxcpus confusion
Date: Mon, 4 Dec 2017 22:02:28 +0100 [thread overview]
Message-ID: <20171204210228.GA3286@osiris> (raw)
In-Reply-To: <e56b3c83-1488-e104-0d1d-f21f8c0116b1@infradead.org>
On Fri, Dec 01, 2017 at 12:58:47PM -0800, Randy Dunlap wrote:
> Hi,
>
> I used "maxcpus=1" on a recent x86 boot (4.15-rc1) and got 4 CPUs (all of
> them AFAICT). When I use "nr_cpus=1", I do get a hard limit of one CPU.
>
>
> A few boot log excerpts:
>
> [ 0.000000] smpboot: Allowing 8 CPUs, 4 hotplug CPUs
> ...
> [ 0.030007] smp: Bringing up secondary CPUs ...
> [ 0.030109] smp: Brought up 1 node, 1 CPU
> [ 0.030181] smpboot: Max logical packages: 4
> [ 0.030255] smpboot: Total of 1 processors activated (4789.06 BogoMIPS)
>
>
> Is systemd (or something else) later onlining the other CPUs?
>
> /sys/devices/system/cpu/online is 0-3
> /sys/devices/system/cpu/offline is 4-7
Check /lib/udev/rules.d/ for a rule that auto-onlines CPUs.
This behavior is distribution specific.
next prev parent reply other threads:[~2017-12-04 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 20:58 maxcpus confusion Randy Dunlap
2017-12-04 21:02 ` Heiko Carstens [this message]
2017-12-04 22:40 ` Randy Dunlap
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=20171204210228.GA3286@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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