diff options
| author |   Ross Zwisler <zwisler@chromium.org> | 2023-01-30 11:19:11 -0700 |
|---|---|---|
| committer |   Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2023-02-02 15:45:35 +0100 |
| commit | cf3e0251868c56b10ccb3e0b3628fcfb0c9c4ec5 (patch) | |
| tree | 901893cb98de347b8432efcf307a4124211135a3 /scripts/generate_rust_analyzer.py | |
| parent | Linux 6.2-rc6 (diff) | |
| download | linux-rng-cf3e0251868c56b10ccb3e0b3628fcfb0c9c4ec5.tar.xz linux-rng-cf3e0251868c56b10ccb3e0b3628fcfb0c9c4ec5.zip | |
PM: tools: 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
A few scripts in tools/power still refer to this older debugfs path, so
let's update them to avoid confusion.
Signed-off-by: Ross Zwisler <zwisler@google.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions