diff options
| author | Ross Zwisler <zwisler@chromium.org> | 2023-01-25 14:32:51 -0700 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-01-31 14:02:30 -0700 |
| commit | 2abfcd293b79baf62895894fa3ea2386ffbe6338 (patch) | |
| tree | b74867f24b7c6d6b6909856063d6c184a29195e0 /Documentation/core-api | |
| parent | b05ada5615f844c3fdcf5e2a0fa35a4bc1a394f2 (diff) | |
| download | lwn-2abfcd293b79baf62895894fa3ea2386ffbe6338.tar.gz lwn-2abfcd293b79baf62895894fa3ea2386ffbe6338.zip | |
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/core-api')
| -rw-r--r-- | Documentation/core-api/workqueue.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst index 3b22ed137662..8ec4d6270b24 100644 --- a/Documentation/core-api/workqueue.rst +++ b/Documentation/core-api/workqueue.rst @@ -370,8 +370,8 @@ of possible problems: The first one can be tracked using tracing: :: - $ echo workqueue:workqueue_queue_work > /sys/kernel/debug/tracing/set_event - $ cat /sys/kernel/debug/tracing/trace_pipe > out.txt + $ echo workqueue:workqueue_queue_work > /sys/kernel/tracing/set_event + $ cat /sys/kernel/tracing/trace_pipe > out.txt (wait a few secs) ^C |