The trace_remote parameter allows to configure a trace remote on registration. The syntax is similar to trace_instance.
Signed-off-by: Vincent Donnefort <[email protected]> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index 97007f4f69d4..dec8fd1f5ff9 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -7792,6 +7792,22 @@ Kernel parameters See also Documentation/trace/ftrace.rst "trace options" section. + trace_remote=[remote-info] + [FTRACE] Configure a trace remote instance at boot. + Format: <name>[^option1[^option2...]][,event1[,event2...]] + + Supported options: + dump_on_oops - Enable panic load to dump the trace + buffer on oops/panic. + printk - Redirect tracing output to printk. + buf_size=<size> - Set trace buffer size (e.g. 2M). + + Events are a comma-separated list of events to enable. + If events are specified, tracing is automatically enabled. + + Multiple remotes can be configured by specifying this + parameter multiple times. + trace_trigger=[trigger-list] [FTRACE] Add an event trigger on specific events. Set a trigger on top of a specific event, with an optional -- 2.54.0.1032.g2f8565e1d1-goog
