On 03/17/2011 02:55 PM, Mathieu Desnoyers wrote:
Yes, the main difference when passing through the ltt-sessiond daemon is
that your application would be two things:
a) a trace data producer (hence it links with libust).
b) a trace controller (hence it links with the new liblttngctl)
So the application can set the marker states, start/stop tracing, spawn
a consumer daemon, etc, but this is not done directly with a libust API:
it's done through the ltt-sessiond throught the liblttngctl API, as if
it was a normal "trace control" application.
Does that make sense ?
Sounds reasonable. I like this producer/consumer/controller abstraction.
There will be one consumer daemon per user, right ? Is this new consumer
daemon also able to consume kernel events so that for a combined
userspace/kernel session all trace data goes into one unified trace
directory ?
--
Paul
_______________________________________________
ltt-dev mailing list
[email protected]
http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
