Expose kernel tracer to user-space (version 7)
A message that is not in the archive (sent off-list or not yet received): [email protected]
Hello,
Quoted 5 lines · Francis Giraldeau
By writing to the file
/proc/lttng_uevent, a user-space application creates a kernel event. The event's payload is by default UTF-8 text, but any data can be written. The maximum size of the data is at most the size of a packet defined for the trace session. Null-character is optional and is not enforced. The event uses sequence for space efficiency and to store any data as payload.
Shouldn't this be in the debugfs filesystem rather than the proc filesystem? The debugfs filesystem already has entries for various tracing facilities of the Linux kernel, and adding entries in /proc that are not process-related is frowned upon these days.
Best regards,
Thomas
Signature · 9 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
A message that is not in the archive (sent off-list or not yet received): 20120704093821.35384043@skate
Quoted 11 lines · * Thomas Petazzoni ([email protected]) wrote:
Hello,
Quoted 5 lines · Francis Giraldeau
By writing to the file
/proc/lttng_uevent, a user-space application creates a kernel event. The event's payload is by default UTF-8 text, but any data can be written. The maximum size of the data is at most the size of a packet defined for the trace session. Null-character is optional and is not enforced. The event uses sequence for space efficiency and to store any data as payload.
Quoted 4 lines
Shouldn't this be in the debugfs filesystem rather than the proc filesystem? The debugfs filesystem already has entries for various tracing facilities of the Linux kernel, and adding entries in /proc that are not process-related is frowned upon these days.
yes, I think this infrastructure should belong in debugfs.
Thanks,
Mathieu
Quoted 14 lines
Best regards,
Thomas
Signature · 9 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
Signature · 3 lines
Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com