linux-kernel - Re: [RESEND][PATCH] clockevent: let set

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] [day] [month] [year] [list]

Date:	Fri, 16 Jan 2009 12:28:09 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Magnus Damm <magnus.damm@...il.com>
cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	johnstul@...ibm.com, lethal@...ux-sh.org, mingo@...hat.com
Subject: Re: [RESEND][PATCH] clockevent: let set_mode() setup delta
 information

On Fri, 16 Jan 2009, Magnus Damm wrote:
> From: Magnus Damm <damm@...l.co.jp>
> 
> Allow the set_mode() clockevent callback to decide and fill in delta
> details such as shift, mult, max_delta_ns and min_delta_ns.
> 
> With this change the clockevent can be registered without delta details
> which allows us to keep the parent clock disabled until the clockevent
> gets setup using set_mode().
> 
> Letting set_mode() fill in or update delta details allows us to save
> power by disabling the parent clock while the clockevent is unused.
> This may however make the parent clock rate change, so next time the
> clockevent gets enabled we need let set_mode() to update the detla
> details accordingly. Doing it at registration time is not enough.
> 
> Furthermore, the delta details seem unused in the case of periodic-only
> clockevent drivers, so this change also allows registration of such
> drivers without the delta details filled in.
> 
> Signed-off-by: Magnus Damm <damm@...l.co.jp>

Applied to tip/timers/clockevents

Thanks,

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