mirror of
https://github.com/torvalds/linux.git
synced 2026-03-08 03:44:45 +01:00
7b382efd5e
There are applications that have it hard coded to write into the top level trace_marker instance (/sys/kernel/tracing/trace_marker). This can be annoying if a profiler is using that instance for other work, or if it needs all writes to go into a new instance. A new option is created called "copy_trace_marker". By default, the top level has this set, as that is the default buffer that writing into the top level trace_marker file will go to. But now if an instance is created and sets this option, all writes into the top level trace_marker will also be written into that instance buffer just as if an application were to write into the instance's trace_marker file. If the top level instance disables this option, then writes to its own trace_marker and trace_marker_raw files will not go into its buffer. If no instance has this option set, then the write will return an error and errno will contain ENODEV. Cc: Masami Hiramatsu <mhiramat@kernel.org> Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Link: https://lore.kernel.org/20250508095639.39f84eda@gandalf.local.home Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org> |
||
|---|---|---|
| .. | ||
| coresight | ||
| postprocess | ||
| rv | ||
| boottime-trace.rst | ||
| debugging.rst | ||
| events-kmem.rst | ||
| events-msr.rst | ||
| events-nmi.rst | ||
| events-power.rst | ||
| events.rst | ||
| fprobe.rst | ||
| fprobetrace.rst | ||
| ftrace-design.rst | ||
| ftrace-uses.rst | ||
| ftrace.rst | ||
| function-graph-fold.vim | ||
| hisi-ptt.rst | ||
| histogram-design.rst | ||
| histogram.rst | ||
| hwlat_detector.rst | ||
| index.rst | ||
| intel_th.rst | ||
| kprobes.rst | ||
| kprobetrace.rst | ||
| mmiotrace.rst | ||
| osnoise-tracer.rst | ||
| ring-buffer-design.rst | ||
| ring-buffer-map.rst | ||
| stm.rst | ||
| sys-t.rst | ||
| timerlat-tracer.rst | ||
| tracepoint-analysis.rst | ||
| tracepoints.rst | ||
| uprobetracer.rst | ||
| user_events.rst | ||