linux-kernel - Re: [patch] x86, numa: Fix CONFIG_DEBUG_PER_CPU

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:	Thu, 6 Jan 2011 12:39:27 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] x86, numa: Fix CONFIG_DEBUG_PER_CPU_MAPS without NUMA
 emulation

On Thu, 30 Dec 2010, David Rientjes wrote:

> "x86, numa: Fake node-to-cpumask for NUMA emulation" broke the build when
> CONFIG_DEBUG_PER_CPU_MAPS is set and CONFIG_NUMA_EMU is not.  This is
> because it is possible to map a cpu to multiple nodes when NUMA emulation
> is used; the patch required a physical node address table to find those
> nodes that was only available when CONFIG_NUMA_EMU was enabled.
> 
> This extracts the common debug functionality to its own function for
> CONFIG_DEBUG_PER_CPU_MAPS and uses it regardless of whether
> CONFIG_NUMA_EMU is set or not.
> 
> NUMA emulation will now iterate over the set of possible nodes for each
> cpu and call the new debug function whereas only the cpu's node will be
> used without NUMA emulation enabled.
> 
> Reported-by: Ingo Molnar <mingo@...e.hu>
> Signed-off-by: David Rientjes <rientjes@...gle.com>

Ingo, do you know what the status of this fix is?  It's required for 
x86/numa to build and I'd hate to see all of this fixes miss .38 because 
of this failure.
--
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/