linux-kernel - Re: x86: A fast way to check capabilities of the current 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110121181250.GA22824@htj.dyndns.org>
Date:	Fri, 21 Jan 2011 19:12:50 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Pekka Enbeerg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org,
	Eric Dumazet <eric.dumazet@...il.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	akpm@...ux-foundation.org
Subject: Re: x86: A fast way to check capabilities of the current cpu

On Fri, Jan 21, 2011 at 11:57:09AM -0600, Christoph Lameter wrote:
> > Hmm?  asm/percpu.h gets included by linux/percpu.h, so it would end up
> > in most .c files.
> 
> The function is defined in arch/x86/include/asm/percpu.h. At least my
> patches here are that way.
> 
> #include "asm/percpu.h" will get you include/asm-generic/percpu.h on
> other arches.

Yeah, I was referring to generic code having visibility to the x86
specific this_cpu op which isn't available on other archs.  I don't
feel too strong about it so if you don't like it, just add a comment.

Thanks.

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