linux-kernel - Re: [patch 2/2] x2apic: use x2apic id reported by cpuid during topology discovery

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] [day] [month] [year] [list]

Date:	Tue, 19 Aug 2008 02:24:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
Cc:	hpa@...or.com, tglx@...utronix.de, linux-kernel@...r.kernel.org,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [patch 2/2] x2apic: use x2apic id reported by cpuid during
	topology discovery


* Suresh Siddha <suresh.b.siddha@...el.com> wrote:

> use x2apic id reported by cpuid during topology discovery, instead of the
> apic id configured in the APIC. For most of the systems, x2apic id
> reported by cpuid leaf 0xb will be same as the physical apic id reported
> by the APIC_ID register of the APIC. We follow the suggested guidelines
> and use the apic id reported by the cpuid.
> 
> No change to non-generic UV platforms, will use the apic id reported in the
> APIC_ID register as the cpuid reported apic id's may not be unique.
> 
> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>

applied both fixes to tip/x86/x2apic - thanks Suresh!

	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/