From: Ingo Molnar <mingo@kernel.org>
To: Dave Jones <davej@redhat.com>,
x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: disabled APICs being counted as processors ?
Date: Sat, 25 Jan 2014 08:41:07 +0100 [thread overview]
Message-ID: <20140125074107.GA10565@gmail.com> (raw)
In-Reply-To: <20140123221316.GA23367@redhat.com>
* Dave Jones <davej@redhat.com> wrote:
> I have a system with 4 cores (configured with CONFIG_NR_CPUS=4) that shows during boot..
>
> [ 0.000000] smpboot: 8 Processors exceeds NR_CPUS limit of 4
>
> it looks like this is because..
>
> [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0xff] disabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0xff] disabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0xff] disabled)
> [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0xff] disabled)
>
> Should the CPU counting code be ignoring those disabled APICs ?
Hm, so to the kernel it looks like as if those were 'possible CPUs',
in theory hotpluggable. Not sure what they are - disabled cores in an
8-core system? Or BIOS reporting crap?
But perhaps the boot message could be improved to say something like:
> [ 0.000000] smpboot: 8 possible processors exceeds NR_CPUS limit of 4
?
Thanks,
Ingo
next prev parent reply other threads:[~2014-01-25 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 22:13 disabled APICs being counted as processors ? Dave Jones
2014-01-25 7:41 ` Ingo Molnar [this message]
2014-01-25 15:30 ` Dave Jones
2014-01-26 6:41 ` David Rientjes
2014-01-26 8:36 ` Ingo Molnar
2014-01-26 8:51 ` Yinghai Lu
2014-01-26 9:09 ` Ingo Molnar
2014-01-26 9:23 ` David Rientjes
2014-01-26 9:29 ` Ingo Molnar
2014-01-26 9:44 ` David Rientjes
2014-01-25 16:42 ` 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=20140125074107.GA10565@gmail.com \
--to=mingo@kernel.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.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