linux-kernel - Re: [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions

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

Message-ID: <506C5EDB.9000107@zytor.com>
Date:	Wed, 03 Oct 2012 08:50:51 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Daniel Blueman <daniel@...ascale-asia.com>
CC:	Ingo Molnar <mingo@...hat.com>,
	Steffen Persvold <sp@...ascale.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...64.org>,
	x86@...nel.org
Subject: Re: [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions

On 10/03/2012 08:30 AM, Daniel Blueman wrote:
>  >
>  > Is that "on NumaScale systems"?  If so, please say so rather than trying
>  > to make it sound generic; if it is not, can you give some other examples?
>
> It is for Numascale (NumaChip) systems for our purposes.
>
> Any other systems which interconnect Opterons via address space routing
> (needed for >8 HT nodes) will get this benefit. I can't put my hand to
> exactly what is out there, but can find out.
>

The reason I'm asking is because it is an important bit of the record of 
the code to know if this is a specific need or a general need.  This may 
be obvious now, but 5-10 years from now someone will need to know why or 
what.

The two paragraphs above is exactly what is needed, i.e. "NumaChip or 
any other design which shares these specific design features: ..."

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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