| 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
| ||
|
Date: Thu, 3 Jul 2014 00:01:21 +0200 From: Pavel Machek <pavel@....cz> To: Borislav Petkov <bp@...en8.de> Cc: Prarit Bhargava <prarit@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, the arch/x86 maintainers <x86@...nel.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: RFC: /proc/cpuinfo confusion with AMD processors On Mon 2014-06-30 15:38:03, Borislav Petkov wrote: > On Mon, Jun 30, 2014 at 09:29:05AM -0400, Prarit Bhargava wrote: > > Yes, I get that. But this doesn't uniquely identify *which* processor > > it is. > > What do you mean, which processor it is? You want to know which > processor on the motherboard, physically? When you look at the mobo and > if all is enumerated regularly and you have a, say, two socket system > with the processors above, to be able to say that processor 31 is the > 16th core on the second node on the motherboard? Something like that? I'd say so. Some machines support physical cpu hotplug, and it would be useful to know which cpu you are plugging out... (For example if you want to pull out / replace the cpu that has problems... Or maybe more realistically you want to offline a CPU so that you can replace a noisy CPU fan.) Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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