linux-kernel - Re: tsc timer related problems/questions

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:	Sun, 9 Sep 2007 19:31:48 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Dennis Lubert <plasmahh@....net>, linux-kernel@...r.kernel.org
Subject: Re: tsc timer related problems/questions

On Sun, 9 Sep 2007 20:17:28 +0200 (CEST)
Jan Engelhardt <jengelh@...putergmbh.de> wrote:

> 
> On Sep 9 2007 17:49, Arjan van de Ven wrote:
> >> 
> >> Question: Why are only Intel CPUs considered as stable? Could
> >> there be implemented a more sophisticated heuristic, that actually
> >> does some tests for tsc stability?
> >
> >on AMD multi-socket systems, afaik the tsc is not synchronized
> >between packages. On Intel the tsc is derived from the FSB which is
> >shared between the packages.
> 
> Also, the TSC is not necessarily constant wrt. CPU clock speed.
> If your program stalls, the core may reduce frequency and hence
> TSC values are not linear to time anymore.
> 

that depends on the CPU generation; most current cpus have
constant-rate tscs (at least constant wrt their own concept of time,
but at least independent of cpu frequency)...

it gets more iffy on idle; on deep idle the tsc tends to stop ;(
-
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/