[PATCH v5 18/18] Documentation/kernel-parameters: Add trace_remote
Vincent Donnefort <[email protected]>
| Newsgroups | org.kernel.vger.linux-trace-kernel,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
The trace_remote parameter allows configuring 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 3d35270dddef..c8470050b285 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -7787,6 +7787,25 @@ 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_panic - Enable dumping the trace buffer on + panic. + dmesg - Redirect tracing output to dmesg. + buf_size=<size> - Set the trace buffer size (e.g. 2M). + poll=<ms> - Set the trace remote polling interval + in milliseconds. + + 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.55.0.691.gc56d675ccc-goog