linux-kernel - Re: [PATCH] x86: use hard_smp_processor_id to get apic id in identify

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:	Wed, 26 Aug 2009 15:24:15 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>
Subject: Re: [PATCH] x86: use hard_smp_processor_id to get apic id in
 identify_cpu -v2

On Wed, 2009-08-26 at 12:07 -0700, Yinghai Lu wrote:
> Suresh Siddha wrote:
> > 
> > In short, on all the platforms we want to use initial apic id for apicid
> > and phys_proc_id. And only on the required platforms like x445, vsmp,
> > some AMD platforms, we can have their own mechanisms.
> > 
> >> 3. for vsmp, and x445, do you want to have c->apicid to have real apic id or the same as initial apic_id?
> > 
> > On these platforms, c->apicid should be based on their real apic id.
> > 
> >> this patch is trying to make c->apicid to have real apic_id.
> > 
> > Can you please modify the patch so that we can have exceptions for
> > needed platforms only?
> > 
> 
> please check this one
> 
> [PATCH] x86: use hard_smp_processor_id to get apic id for amd k8 cpus
> 
> otherwise, system with apci id lifting will have wrong apicid in
> /proc/cpuinfo
> 
> and use that in srat_detect_node
> 
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> 

Looks better.

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