linux-kernel - Re: [BUG] perf: perf sched warning possibly due to clock granularity on AMD

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:	Tue, 07 Feb 2012 08:51:08 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Venki Pallipadi <venki@...gle.com>
Cc:	Borislav Petkov <bp@...64.org>,
	Stephane Eranian <eranian@...gle.com>,
	linux-kernel@...r.kernel.org, acme@...hat.com, mingo@...e.hu,
	robert.richter@....com, eric.dumazet@...il.com,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: [BUG] perf: perf sched warning possibly due to clock
 granularity on AMD

On Mon, 2012-02-06 at 13:19 -0800, Venki Pallipadi wrote:
> 
> Yes. If these two flags are set, TSC should be consistent and sched_clock_stable
> could be set and it will be reset if there is a call to mark_tsc_unstable(). 

Only trouble is that sched_clock_cpu() et al. will jump when you flip
sched_clock_stable to 0 after you started using it.. its something we
might want to fix.

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