linux-kernel - Re: [PATCH] clocksource: shift helper

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: <20080501210536.GA6135@linux-mips.org>
Date:	Thu, 1 May 2008 22:05:36 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, johnstul@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clocksource: shift helper

On Thu, May 01, 2008 at 12:48:25PM -0700, Daniel Walker wrote:

> > If we expect this to have more than one callsite then it would be best to
> > uninline it.
> > 
> > Unless we always expect it to be called from __init code, in which case
> > it's best to inline it ;)
> 
> I expect it would always get called from __init flagged functions. The
> clocksource can't get registed/used with out the shift and mult values. 
> 
> If we did uninline this one, we would have to do the other helpers too.
> I imagine the use case is the same for all of them ..

I could imagine this being called for hotpluggable CPUs or nodes, so rather
__cpuinit than __init.

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