linux-kernel - Re: Clocksource tsc unstable (delta = -8589361717 ns) in current git

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: <alpine.LFD.2.00.1010261745260.3115@localhost6.localdomain6>
Date:	Tue, 26 Oct 2010 17:46:00 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Borislav Petkov <bp@...64.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: Clocksource tsc unstable (delta = -8589361717 ns) in current
 git

On Tue, 26 Oct 2010, Peter Zijlstra wrote:

> On Tue, 2010-10-26 at 15:58 +0200, Markus Trippelsdorf wrote:
> > > 
> > > This is strange, tsc is actually stable on your F10h revC.
> > 
> > Yes. constant_tsc is among the CPU flags. 
>  
> constant_tsc only means the TSC is not affected by cpu freq changes.
> 
> It has zero relevance to cross-cpu sync of the TSC. The clocksource
> stuff requires your TSC to be synchronous over all your CPUs.

That and not affected by C-States either.

Thanks,

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