| 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
| ||
|
Message-Id: <20070917183507.332345000@sgi.com> Date: Mon, 17 Sep 2007 11:35:07 -0700 From: travis@....com To: sfr@...b.auug.org.au, Andrew Morton <akpm@...ux-foundation.org> Cc: Andi Kleen <ak@...e.de>, Christoph Lameter <clameter@....com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org, sparclinux@...r.kernel.org Subject: [PATCH 0/1] ppc64: Convert cpu_sibling_map to a per_cpu data array ppc64 v2 Stephen Rothwell wrote: > On Mon, 17 Sep 2007 16:28:31 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote: >> the topology (on my POWERPC5+ box) is not correct: >> >> cpu0/topology/thread_siblings:0000000f >> cpu1/topology/thread_siblings:0000000f >> cpu2/topology/thread_siblings:0000000f >> cpu3/topology/thread_siblings:0000000f >> >> it used to be: >> >> cpu0/topology/thread_siblings:00000003 >> cpu1/topology/thread_siblings:00000003 >> cpu2/topology/thread_siblings:0000000c >> cpu3/topology/thread_siblings:0000000c > > This would be because we are setting up the cpu_sibling map before we > call setup_per_cpu_areas(). The following patch hopefully should fix this problem. I'm not able to build or test it but the few references to cpu_sibling_map seem to all occur well after setup_per_cpu_areas is called. Thanks Stephen for checking this out! -- - 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/
Powered by blists - more mailing lists