linux-kernel - Re: [RFC patch 00/12] Tracepoints v2

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: <20080706022711.199401fe@linux360.ro>
Date:	Sun, 6 Jul 2008 02:27:11 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	"Frank Ch. Eigler" <fche@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [RFC patch 00/12] Tracepoints v2

On Fri, 04 Jul 2008 19:52:07 -0400
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:

> Hi,
> 
> Here is the second release of kernel tracepoints, including the
> architecture independent instrumentation taken from LTTng. I submit
> this for another round of comments.

Hi,

Not using format specifiers sounds pretty nice. Are there any other
advantages over markers? What about self-modifying code, does it employ
this technique to eliminate conditional branching (markers did this on
some arches, IIRC)?

I'm considering using this for kmemtrace, so please keep me Cc-ed if
possible.


	Cheers,
	Eduard

P.S.: BTW, the To header is either broken or I screwed it (I'm reading
this via Gmane's NNTP):
"Steven Rostedt <ros"
--
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/