linux-kernel - [RFC PATCH 0/2 v2] Unified trace buffer (take two)

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]

Message-Id: <20080925155807.158539649@goodmis.org>
Date:	Thu, 25 Sep 2008 11:58:07 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	prasad@...ux.vnet.ibm.com,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	David Wilder <dwilder@...ibm.com>, hch@....de,
	Martin Bligh <mbligh@...gle.com>,
	Christoph Hellwig <hch@...radead.org>
Subject: [RFC PATCH 0/2 v2] Unified trace buffer (take two)


Again: this is a proof of concept, just spitting out code for comments.

Here's my second attempt.

Changes since version 1:

 - Ripped away all the debugfs and event registration from ring buffers.

 - Removed the mergesort from the ringbuffer and pushed that up to the
   tracer.

 - Changed the event header to what Linus suggested (we can discuss this
   and try other suggestions for v3, namely Peter Zijlstras ideas).

 struct {
 	u32 time_delta:27, type:5;
	u32 data;
	u64 array[];
 };

 - Added timestamp at beginning of each page and implemented a way
   for all events to get the full timestamp from the previous.

 - The changes to ftrace on this release was much less than the first
   one.

Comments?

-- Steve

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