lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 25 Jan 2014 08:41:07 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Dave Jones <davej@...hat.com>, x86@...nel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: disabled APICs being counted as processors ?


* Dave Jones <davej@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ