linux-kernel - Re: [patch] x86: fix fake apicid to node mapping for numa emulation

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: <alpine.DEB.2.00.1005060222560.19473@chino.kir.corp.google.com>
Date:	Thu, 6 May 2010 02:24:06 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
	Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [patch] x86: fix fake apicid to node mapping for numa
 emulation

On Thu, 6 May 2010, Ingo Molnar wrote:

> > apicids must be mapped to the lowest node ids to maintain generic kernel use 
> > of functions such as cpu_to_node() that determine device affinity.
> > 
> > Signed-off-by: David Rientjes <rientjes@...gle.com>
> > ---
> >  Third resend of the same patch.
> > 
> >  arch/x86/mm/srat_64.c |    3 ++-
> >  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> There's no info in the changelog about what negative effects this bug had when 
> it was found, on what hardware it occured, and what the general urgency of the 
> patch is.
> 

Ah, true.  Given the relative obscurity of using NUMA emulation to being 
with, it would probably benefit from being even more verbose as well.  
I'll rewrite the changelog and reply to this message with it.

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