[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48AB1E43.2010408@cs.helsinki.fi>
Date: Tue, 19 Aug 2008 22:25:55 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
CC: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
"Randy.Dunlap" <rdunlap@...otime.net>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, mpm@...enic.com,
tglx@...utronix.de, rostedt@...dmis.org, cl@...ux-foundation.org,
tzanussi@...il.com
Subject: Re: [PATCH 1/5] Revert "kmemtrace: fix printk format warnings"
Eduard - Gabriel Munteanu wrote:
> On Tue, Aug 19, 2008 at 02:16:53PM -0400, Mathieu Desnoyers wrote:
>> Question :
>>
>> Is this kmemtrace marker meant to be exposed to userspace ?
>>
>> I suspect not. In all case, not directly. I expect in-kernel probes to
>> be connected on these markers which will get the arguments they need,
>> and maybe access the inner data structures. Anyhow, tracepoints should
>> be used for that, not markers. You can later put markers in the probes
>> which are themselves connected to tracepoints.
>>
>> Tracepoints = in-kernel tracing API.
>>
>> Markers = Data-formatting tracing API, meant to export the data either
>> to user-space in text or binary format.
>>
>> See
>>
>> http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=shortlog
>>
>> tracepoint-related patches.
>
> I think we're ready to try tracepoints. Pekka, could you merge Mathieu's
> tracepoints or otherwise provide a branch where I could submit a
> tracepoint conversion patch for kmemtrace?
Sorry, that's too much of a hassle for me. I'll happily take your
conversion patch once tracepoints hit mainline. Mathieu, are you aiming
for 2.6.28?
--
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/
Powered by blists - more mailing lists