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/translations/zh_CN | |
| 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/translations/zh_CN')
| -rw-r--r-- | Documentation/translations/zh_CN/core-api/workqueue.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/translations/zh_CN/core-api/workqueue.rst b/Documentation/translations/zh_CN/core-api/workqueue.rst index f6567cf9d3fb..6c1b5ec31d75 100644 --- a/Documentation/translations/zh_CN/core-api/workqueue.rst +++ b/Documentation/translations/zh_CN/core-api/workqueue.rst @@ -313,8 +313,8 @@ And with cmwq with ``@max_active`` >= 3, :: 第一个可以用追踪的方式进行跟踪: :: - $ 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) 如果有什么东西在工作队列上忙着做循环，它就会主导输出，可以用工作项函数确定违规者。 |