linux-kernel - Re: [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable (v2) (fwd)

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: <200709050910.10954.ak@suse.de>
Date:	Wed, 5 Sep 2007 09:10:10 +0100
From:	Andi Kleen <ak@...e.de>
To:	Mike Travis <travis@....com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, clameter@....com,
	steiner@....com, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	kamalesh@...ux.vnet.ibm.com
Subject: Re: [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable (v2) (fwd)


> > It'd be better to convert the unconverted architectures?

Agreed.

> I can easily do the changes for ia64 and test them.  I don't have the
> capability of testing on the powerpc.

You can get cross compilers and make it compile and I'm sure some
powerpc person will be happy to test it then when you post the patches

> And are you asking for just the changes to fix the build problem, or the
> whole set of the changes that were made for x86_64 and i386 in regards to
> converting NR_CPU arrays to per cpu data?

At least the variables that are used by non architecture specific code 
(like cpu_sibling_map) should be probably all converted. For architecture
specific variables it's ok to leave it to the architecture people.

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