linux-kernel - Re: [PATCH 0/2] Make the TSC safe to be used by gettimeofday().

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 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Nov 2006 14:30:38 +0200
From:	"Shem Multinymous" <multinymous@...il.com>
To:	"Suleiman Souhlal" <ssouhlal@...ebsd.org>
Cc:	"Andi Kleen" <ak@...e.de>,
	"Linux Kernel ML" <linux-kernel@...r.kernel.org>, vojtech@...e.cz,
	"Jiri Bohac" <jbohac@...e.cz>,
	"Nigel Cunningham" <ncunningham@...lades.com>,
	"Pavel Machek" <pavel@...e.cz>
Subject: Re: [PATCH 0/2] Make the TSC safe to be used by gettimeofday().

On 11/14/06, Suleiman Souhlal <ssouhlal@...ebsd.org> wrote:
> I believe that the results returned will always be monotonic, as long as
> the frequency of the TSC does not change from under us (that is, without
> the kernel knowing). This is because we "synchronize" each CPU's vxtime
> with a global time source (HPET) every time we know the TSC rate changes.

Does this hold after a suspend/resume cycle? You could be resuming
with a different CPU clock than what you suspended with, and I'm not
sure anything guarantees an early enough re-sync.

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