diff options
author | Ross Zwisler <zwisler@chromium.org> | 2023-01-26 00:32:51 +0300 |
---|---|---|
committer | Jonathan Corbet <corbet@lwn.net> | 2023-02-01 00:02:30 +0300 |
commit | 2abfcd293b79baf62895894fa3ea2386ffbe6338 (patch) | |
tree | b74867f24b7c6d6b6909856063d6c184a29195e0 /Documentation/admin-guide/kernel-per-CPU-kthreads.rst | |
parent | b05ada5615f844c3fdcf5e2a0fa35a4bc1a394f2 (diff) | |
download | linux-2abfcd293b79baf62895894fa3ea2386ffbe6338.tar.xz |
docs: ftrace: always use canonical ftrace path
The 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/tracing
Many parts of Documentation still reference this older debugfs path, so
let's update them to avoid confusion.
Signed-off-by: Ross Zwisler <zwisler@google.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lore.kernel.org/r/20230125213251.2013791-1-zwisler@google.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/admin-guide/kernel-per-CPU-kthreads.rst')
-rw-r--r-- | Documentation/admin-guide/kernel-per-CPU-kthreads.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst index e4a5fc26f1a9..993c2a05f5ee 100644 --- a/Documentation/admin-guide/kernel-per-CPU-kthreads.rst +++ b/Documentation/admin-guide/kernel-per-CPU-kthreads.rst @@ -25,7 +25,7 @@ References - In order to locate kernel-generated OS jitter on CPU N: - cd /sys/kernel/debug/tracing + cd /sys/kernel/tracing echo 1 > max_graph_depth # Increase the "1" for more detail echo function_graph > current_tracer # run workload |