diff options
| author | Ross Zwisler <zwisler@chromium.org> | 2023-02-16 01:33:49 +0300 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2023-06-09 19:08:08 +0300 |
| commit | 07496eeab577eef1d4912b3e1b502a2b52002ac3 (patch) | |
| tree | 4ec428503f85cdd444147505e0d43861e47098d2 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | beee7fdb5b56a46415a4992d28dd4c2d06eb52df (diff) | |
| download | linux-07496eeab577eef1d4912b3e1b502a2b52002ac3.tar.xz | |
tools/virtio: 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 spots in tools/virtio still refer to this older debugfs
path, so let's update them to avoid confusion.
Signed-off-by: Ross Zwisler <zwisler@google.com>
Message-Id: <20230215223350.2658616-6-zwisler@google.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions