linux-kernel - Re: [PATCH x86/urgent 2/2] x86: Implement pfn -> nid mapping granularity check

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: <20110711142004.GA11163@escobedo.osrc.amd.com>
Date:	Mon, 11 Jul 2011 16:20:04 +0200
From:	Hans Rosenfeld <hans.rosenfeld@....com>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Seidel, Conny" <Conny.Seidel@....com>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH x86/urgent 2/2] x86: Implement pfn -> nid mapping
 granularity check

On Sat, Jul 09, 2011 at 04:42:31AM -0400, H. Peter Anvin wrote:
> On 07/09/2011 01:32 AM, Tejun Heo wrote:
> > 
> > Ping?  If the change is too invasive at this stage, we can disable AMD
> > NUMA on x86_32 for 3.0 and queue these two for 3.1.
> > 
> 
> I am kind of leaning that way... Hans, what is your opinion?

Thats ok for me. Disable it in 3.0 and fix it properly in 3.1.


Hans


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown

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