linux-kernel - Re: Can Linux kernel handle unsynced TSC?

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

Message-Id: <1204281823.6243.78.camel@lappy>
Date:	Fri, 29 Feb 2008 11:43:43 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Zhao Forrest <forrest.zhao@...il.com>
Cc:	linux-kernel@...r.kernel.org, kvm-devel@...ts.sourceforge.net
Subject: Re: Can Linux kernel handle unsynced TSC?

On Fri, 2008-02-29 at 16:55 +0800, Zhao Forrest wrote:
> Sorry for reposting it.
> 
> For example,
> 1 rdtsc() is invoked on CPU0
> 2 process is migrated to CPU1, and rdtsc() is invoked on CPU1
> 3 if TSC on CPU1 is slower than TSC on CPU0, can kernel guarantee
> that the second rdtsc() doesn't return a value smaller than the one
> returned by the first rdtsc()?

No, rdtsc() goes directly to the hardware. You need a (preferably cheap)
clock abstraction layer on top if you need this.

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