linux-kernel - RE: [patch x86/mce] ACPI, x86: Export boot_cpu_physical

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]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F31D6D644@ORSMSX106.amr.corp.intel.com>
Date:	Thu, 14 Nov 2013 23:26:21 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	David Rientjes <rientjes@...gle.com>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
CC:	Chen Gong <gong.chen@...ux.intel.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [patch x86/mce] ACPI, x86: Export boot_cpu_physical_apicid to
 modules

> ERROR: "boot_cpu_physical_apicid" [drivers/acpi/acpi_extlog.ko] undefined!
>
> The symbol needs to be exported for it to be available.

Good - but I wonder how many more useless layers there are to this onion :-(

First I had to add a "#include <asm/cpu.h>"
Then add the dependency on CONFIG_X86_LOCAL_APIC
Now we need to export boot_cpu_physical_apicid

all for the CONFIG_SMP=n case ... which I think is useless because there
is no conceivable way anyone would run a uniprocessor kernel on a system
that supports the extended error log. (Hint: multi-socket server multiplied by
high-core-count processors multiplied by 2xHyperThread) is a number bigger
than one).

Perhaps we should just have:

	depends on SMP && X86_MCE

and stop the madness?

-Tony
--
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/