linux-kernel - Re: [PATCH] Remove CLOCK_TICK

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

Date:	Wed, 02 Nov 2011 16:25:43 -0400
From:	John Stultz <johnstul@...ibm.com>
To:	dsaxena@...xity.net
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] Remove CLOCK_TICK_RATE from tsc code

On Tue, 2011-11-01 at 14:25 -0700, Deepak Saxena wrote:
> The tsc code uses CLOCK_TICK_RATE which on x86
> is defined to just be the same as PIT_TICK_RATE.
> This patch updates the code use the later
> as we want to depecrate and remove the global
> CLOCK_TICK_RATE symbol.

So the ACTHZ issue is still at large (ie: we still want to have a better
sense of the actual HZ frequency for the jiffies clocksource, since the
irq generators will have some - possibly significant - granularity
error), but I'm fine with these cases of just using PIT_TICK_RATE or
PIT_LATCH on x86. 

I've applied these four to my tree.

thanks
-john


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