linux-kernel - Re: x86, amd: Get multi-node CPU info from NodeId MSR instead of PCI config space

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: <20091016130510.GF8387@alberich.amd.com>
Date:	Fri, 16 Oct 2009 15:05:10 +0200
From:	Andreas Herrmann <herrmann.der.user@...glemail.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: x86, amd: Get multi-node CPU info from NodeId MSR instead of
 PCI config space

On Fri, Oct 16, 2009 at 03:00:00PM +0200, Ingo Molnar wrote:
> 
> * Andreas Herrmann <herrmann.der.user@...glemail.com> wrote:
> 
> > > are there any such CPUs?
> > 
> > Only Magny-Cours so far.
> > 
> > > I.e. we want to know the effect of this patch on various models of 
> > > AMD CPUs - is the change really .32 safe? Does it solve any problem 
> > > that makes it .32 material versus being for .33?
> > 
> > IMHO getting rid of the PCI config space accesses as soon as possible 
> > is a benefit, I think.
> 
> Agreed.
> 
> Is the patch an identity transformation? Or are there CPUs where the 
> information from the PCI config space is different from the MSR derived 
> one?

On production hardware it's an identity transformation.


Regards,
Andreas
--
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/