linux-kernel - Re: [PATCH 2/2] i386: sched_clock() follows percpu frequency changes

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: <200705122058.35387.ak@suse.de>
Date:	Sat, 12 May 2007 20:58:35 +0200
From:	Andi Kleen <ak@...e.de>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	johnstul@...ibm.com, mingo@...e.hu, Jiri Bohac <jbohac@...e.cz>
Subject: Re: [PATCH 2/2] i386: sched_clock() follows percpu frequency changes

On Saturday 12 May 2007 17:43:46 Daniel Walker wrote:
> Considering that Andi has a similar patch, I'm going to assume there
> is already justification for this..

I just have a patch for sched_clock, which is somewhat different.

> What it ends up doing is allows the TSC to be used in cases which
> we didn't use it before, and hope it's still mostly accurate.

Yes the current code is badly broken in this regard. e.g. i always
hated that it always falls back on powernow systems.

Jiri will hopefully repost his true per CPU TSC patch soon, that should
make it all obsolete.

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