tracing/user_events: Use write ABI in exampleThe ABI has changed to use a remote write approach. Update the exampleto show the expected use of this new ABI. Also remove debugfspath and use tracef
tracing/user_events: Use write ABI in exampleThe ABI has changed to use a remote write approach. Update the exampleto show the expected use of this new ABI. Also remove debugfspath and use tracefs to ensure example works in more environments.Link: https://lkml.kernel.org/r/20230328235219.203-9-beaub@linux.microsoft.comSigned-off-by: Beau Belgrave <beaub@linux.microsoft.com>Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
show more ...
tracing: Always use canonical ftrace pathThe canonical location for the tracefs filesystem is at /sys/kernel/tracing.But, from Documentation/trace/ftrace.rst: Before 4.1, all ftrace tracing co
tracing: Always use canonical ftrace pathThe canonical location for the tracefs filesystem is at /sys/kernel/tracing.But, from Documentation/trace/ftrace.rst: Before 4.1, all ftrace tracing control files were within the debugfs file system, which is typically located at /sys/kernel/debug/tracing. For backward compatibility, when mounting the debugfs file system, the tracefs file system will be automatically mounted at: /sys/kernel/debug/tracingMany comments and Kconfig help messages in the tracing code still referto this older debugfs path, so let's update them to avoid confusion.Link: https://lore.kernel.org/linux-trace-kernel/20230215223350.2658616-2-zwisler@google.comAcked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>Signed-off-by: Ross Zwisler <zwisler@google.com>Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
tracing/user_events: Use bits vs bytes for enabled status page dataUser processes may require many events and when they do the cacheperformance of a byte index status check is less ideal than a bi
tracing/user_events: Use bits vs bytes for enabled status page dataUser processes may require many events and when they do the cacheperformance of a byte index status check is less ideal than a bit index.The previous event limit per-page was 4096, the new limit is 32,768.This change adds a bitwise index to the user_reg struct. Programs checkthat the bit at status_bit has a bit set within the status page(s).Link: https://lkml.kernel.org/r/20220728233309.1896-6-beaub@linux.microsoft.comLink: https://lore.kernel.org/all/2059213643.196683.1648499088753.JavaMail.zimbra@efficios.com/Suggested-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
user_events: Add sample code for typical usageAdd sample code for user_events typical usage to show how to registerand monitor status, as well as to write out data.Link: https://lkml.kernel.org/
user_events: Add sample code for typical usageAdd sample code for user_events typical usage to show how to registerand monitor status, as well as to write out data.Link: https://lkml.kernel.org/r/20220118204326.2169-12-beaub@linux.microsoft.comAcked-by: Masami Hiramatsu <mhiramat@kernel.org>Signed-off-by: Beau Belgrave <beaub@linux.microsoft.com>Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>