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-next>] [day] [month] [year] [list]
Date:	Thu,  1 Dec 2011 15:20:13 +0800
From:	Yong Zhang <yong.zhang0@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	John Stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: [PATCH 0/3] Patches focus on clocksource_calc_mult_shift()

Hi Thomas/John,

When I was tring to apply commit d65670a7 to old kernel, I found
it's hard to apply, the reason is we only provide
clockevents_calc_mult_shift() for a period of time. And going
through the latest kernel, there is still the user of that
function. So I think we still need the ->maxadj tweak in
clockevents_calc_mult_shift(), this is the aim of patch#1.

And to loose the burden of you, I convert the only user of
clockevents_calc_mult_shift()/clocksource_register() to
clocksour_register_hz() (patch#2), and then get rid of
clockevents_calc_mult_shift() (patch#3).

IMHO, patch#1 will be more conservative and safe, and patch#3
is a little aggressive. I will let you decide to pick which one ;-)

Thanks,
Yong


Cc: John Stultz <johnstul@...ibm.com>
Cc: Thomas Gleixner <tglx@...utronix.de>

Yong Zhang (3):
  clocksource: Also tweak ->maxadj in clocksource_calc_mult_shift()
  clocksource: dbx500: convert to clocksource_register_hz()
  clocksource: get rid of clocksource_calc_mult_shift()

 drivers/clocksource/clksrc-dbx500-prcmu.c |    5 +----
 include/linux/clocksource.h               |    7 -------
 kernel/time/clocksource.c                 |    1 -
 3 files changed, 1 insertions(+), 12 deletions(-)

-- 
1.7.5.4

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ