From: Petr Tesarik <ptesarik@suse.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Jan Beulich <JBeulich@suse.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: Issue a warning if number of present CPUs > maxcpus and CONFIG_HOTPLUG=n
Date: Mon, 17 Feb 2014 15:16:26 +0100 [thread overview]
Message-ID: <20140217151626.5ff99027@hananiah.suse.cz> (raw)
In-Reply-To: <20140217134006.GA14786@khazad-dum.debian.net>
On Mon, 17 Feb 2014 10:40:07 -0300
Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> On Mon, 17 Feb 2014, Petr Tesarik wrote:
> > Well, if the user passes both nr_cpus and maxcpus parameters to the
> > kernel, I think it's fair to issue two warnings. But if everyone agrees
> > that only the maxcpus warning should be printed in that case, I can
> > send a version 2 of my patch.
>
> Please remember that the market is full of motherboards with the extremely
> annoying behaviour of declaring ACPI objects for CPU cores that will never
> be available. This includes a large number of workstation and server boards
> at the very least, from at least one rather large vendor.
>
> As far as I know, we still don't have a way to realiably detect this and get
> rid of the ghost processors which will *NEVER* become online. Setting
> maxcpus or nr_cpus manually is the current way to avoid wasting runtime
> resources because of phantom cores that will never become reality.
>
> So, when you fix the bug that always supress the warnings, you will at the
> same time cause a regression on those boxes, which will now print undesired
> warnings. If the user has manually set nr_cpus or maxcpus, maybe it would
> be best to not print any warnings or alternatively to downgrade them to
> debug level?
While I appreciate your concerns, I fail to see how they are related.
First, please keep in mind that my patch does not alter the (more
common) case with CONFIG_HOTPLUG_CPU=y in any way. For the (presumably
less common) !HOTPLUG_CPU case, it adds a warning that is always issued
in the HOTPLUG_CPU case.
Second, regarding your use case, I don't think it changes anything. So,
let's say you have a board with 16 CPUs and a MADT that describes 1024
CPUs. You know that there can (physically) be at most 48 CPUs, so you
boot with nr_cpus=48:
num_processors = 16 /* online CPUs at boot */
disabled_cpus = 992 /* 1008 - 16 */
This results in:
total_cpus = 1008 /* this is purely informative, it is *NOT* used
to size anything */
possible = 48 /* clamped to nr_cpu_ids */
A warning message (with or without my patch):
1024 Processors exceeds NR_CPUS limit of 48
Informative message:
Allowing 16 CPUs, 32 hotplug CPUs
No other warning (with or without my patch).
Petr Tesarik
SUSE L3 Team 1
next prev parent reply other threads:[~2014-02-17 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 14:02 Petr Tesarik
2014-02-16 17:11 ` Borislav Petkov
2014-02-17 8:34 ` Jan Beulich
2014-02-17 10:04 ` Petr Tesarik
2014-02-17 13:40 ` Henrique de Moraes Holschuh
2014-02-17 14:16 ` Petr Tesarik [this message]
2014-02-17 19:07 ` Henrique de Moraes Holschuh
2014-02-17 19:31 ` Petr Tesarik
2014-02-17 22:51 ` Henrique de Moraes Holschuh
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=20140217151626.5ff99027@hananiah.suse.cz \
--to=ptesarik@suse.cz \
--cc=JBeulich@suse.com \
--cc=bp@alien8.de \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®