linux-kernel - Re: [PATCH] x86: add /proc/cpuinfo/physical id quirks

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1250276831.3077.17.camel@sbs-t61.sc.intel.com>
Date:	Fri, 14 Aug 2009 12:07:11 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Alex Chiang <achiang@...com>
Cc:	"hpa@...or.com" <hpa@...or.com>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: add /proc/cpuinfo/physical id quirks

On Fri, 2009-08-14 at 09:36 -0700, Alex Chiang wrote:
> As systems become larger and more complex, it is not always possible
> to assume that an APIC ID maps directly to a given physical slot.
> 
> From a UI point-of-view, it's nice if the 'physical id' field in
> /proc/cpuinfo matches the silk-screening or labelling on the system
> chassis.
> 
> Add a quirk that allows oddball platforms to ensure that what the kernel
> displays in /proc/cpuinfo matches the physical reality.

Alex, Does it makes sense to add a new entry in /proc/cpuinfo rather
than overloading the 'physical id' by modifying phys_proc_id.

That way, even if there is a mis-match between the bios and the OS fixup
tables, we won't screw up other topology setup etc in the kernel that
are dependent on the phys_proc_id.

thanks,
suresh



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