linux-kernel - Re: [PATCH 0/3] [PATCH] more sched

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

Message-ID: <20080711135630.GD32159@elte.hu>
Date:	Fri, 11 Jul 2008 15:56:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	john stultz <johnstul@...ibm.com>,
	linux-kernel@...r.kernel.org,
	Dmitry Adamushko <dmitry.adamushko@...il.com>
Subject: Re: [PATCH 0/3] [PATCH] more sched_clock updates


* Steven Rostedt <rostedt@...dmis.org> wrote:

> ftrace is still seeing jumps in the sched_clock.c code that is not 
> seen in using sched_clock() function itself. The following patches fix 
> some of the issues that I've seen. There is still a slight drift but 
> all my attempts to remove it completely have failed. Patch 3 does the 
> best sofar at keeping the jumps to a minimum.

cool stuff! I've created a new -tip topic branch for your sched-clock 
fixes and enhancements, under tip/sched/clock, and have picked up your 
patches:

 Steven Rostedt (7):
      sched_clock: record from last tick
      sched_clock: widen the max and min time
      sched_clock: stop maximum check on NO HZ
      sched_clock: fix calculation of other CPU
      sched_clock: only update deltas with local reads.
      sched_clock: record TSC after gtod
      sched_clock: and multiplier for TSC to gtod drift

thanks,

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