linux-kernel - [patch 00/17] Trace Clock v3

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

Date:	Wed, 12 Nov 2008 18:15:51 -0500
From:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org
Subject: [patch 00/17] Trace Clock v3

Hi,

In this new version, I have integrated the changes I did following the comments
I received for v2. I also reimplemented the "generic" trace clock so it is less
intrusive and simply use a standard timer. I is not as bound to the xtime_lock
as it previously was and it does not have to modify kernel/time.c anymore.

I think this is pretty close to a mergeable state. I plan to keep more exotic
features, such as dealing with non-synchronized TSCs without cache-line
bouncing, for future improvement. As a reminder, when the trace clock detects an
unsynchronized TSC on the machine, it prints the information about which kernel
command line arguments must be used so the user can have synchronized timestamp
counters. However, if the user wants to use his system with non-synchronized
TSCs, the cache-line bouncing fallback is used.

This patchset applies on top of 2.6.28-rc4.

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/