linux-kernel - Re: [RFC PATCH 0/5] kmemtrace RFC patch series

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]

Date:	Fri, 11 Jul 2008 23:11:38 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc:	penberg@...helsinki.fi, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [RFC PATCH 0/5] kmemtrace RFC patch series

On Fri, 11 Jul 2008 11:38:41 -0400
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> wrote:

> Hi Eduard,
> 
> Did you have a look at the new tracepoints infrastructure ? I think it
> could simplify your patchset a _lot_ !

Hi,

Yes, I did. In fact, I asked you to keep me Cc-ed, which you did. 
 
> Basically, it removes the format string from markers and allows to
> pass complex structure pointers as arguments. It aims at simplifying
> the life of in-kernel tracers which would want to use the facility.
> Turning a marker implementation to tracepoints is really
> straightforward, for an example see :
> 
> http://lkml.org/lkml/2008/7/9/569
> 
> For the tracepoints patchset :
> 
> http://lkml.org/lkml/2008/7/9/199
> 
> I think much of include/linux/kmemtrace.h, which is really just
> wrappers around marker code, could then go away.

Basically, I want just as much to get rid of markers. I'm just waiting
for tracepoints to get closer to mainline.

	Cheers,
	Eduard

> Regards,
> 
> Mathieu
--
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/