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]
Date:	Sun, 9 Sep 2007 20:17:28 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Dennis Lubert <plasmahh@....net>, linux-kernel@...r.kernel.org
Subject: Re: tsc timer related problems/questions


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.


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