Re: [PATCH] ftrace: add an fsync tracer

[Frank Ch. Eigler]

Hi -

On Thu, Nov 06, 2008 at 04:53:11PM -0500, Mathieu Desnoyers wrote:
> [...]
> > Something like
> > 
> > DEFINE_TRACE_FMT(sched_switch,
> > 	TPPROTO(struct rq *rq, struct task_struct *prev,
> > 		 struct task_struct *next),
> > 	TPARGS(rq, prev, next),
> > 	TPFMT("%d to %d\n", prev->pid, next->pid));
> > 
> > Which would be similar to attaching a trace_mark() to the trace point
> > and can in these cases save a lot of lines of code.
> > 
> > Both lttng and the ftrace event tracer can use these default text
> > strings.
> 
> Argh. No, please. Doing this would end up exposing the inner kernel API
> (the tracepoints) directly to userspace. [...]


Arjan asked for something to send formatted strings to tracing buffers
that are consumed by user space.  Whether internally that is done by
markers, or by tracepoints converted to markers, or by tracepoints
with custom ftrace_printf-y code, is indistinguishable to the user.

Can you be specific in what way any of that is exposing an "API
directly to userspace"?

- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/