From: Ross Zwisler <zwisler@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Ross Zwisler <zwisler@google.com>,
"Tobin C. Harding" <me@tobin.cc>,
Andrew Morton <akpm@linux-foundation.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, Tycho Andersen <tycho@tycho.pizza>,
kvm@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
Steven Rostedt <rostedt@goodmis.org>,
Mukesh Ojha <quic_mojha@quicinc.com>
Subject: [PATCH v3 3/3] tools/kvm_stat: use canonical ftrace path
Date: Fri, 10 Mar 2023 12:20:50 -0700 [thread overview]
Message-ID: <20230310192050.4096886-4-zwisler@kernel.org> (raw)
In-Reply-To: <20230310192050.4096886-1-zwisler@kernel.org>
From: Ross Zwisler <zwisler@google.com>
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 comment in kvm_stat still refers to this older debugfs path, so let's
update it to avoid confusion.
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
Signed-off-by: Ross Zwisler <zwisler@google.com>
---
tools/kvm/kvm_stat/kvm_stat | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/kvm/kvm_stat/kvm_stat b/tools/kvm/kvm_stat/kvm_stat
index 6f28180ffeea..15bf00e79e3f 100755
--- a/tools/kvm/kvm_stat/kvm_stat
+++ b/tools/kvm/kvm_stat/kvm_stat
@@ -627,7 +627,7 @@ class TracepointProvider(Provider):
name)'.
All available events have directories under
- /sys/kernel/debug/tracing/events/ which export information
+ /sys/kernel/tracing/events/ which export information
about the specific event. Therefore, listing the dirs gives us
a list of all available events.
--
2.40.0.rc1.284.g88254d51c5-goog
prev parent reply other threads:[~2023-03-10 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 19:20 [PATCH v3 0/3] use canonical ftrace path whenever possible Ross Zwisler
2023-03-10 19:20 ` [PATCH v3 1/3] selftests: use canonical ftrace path Ross Zwisler
2023-03-10 19:20 ` [PATCH v3 2/3] leaking_addresses: also skip " Ross Zwisler
2023-03-10 19:20 ` Ross Zwisler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230310192050.4096886-4-zwisler@kernel.org \
--to=zwisler@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=me@tobin.cc \
--cc=pbonzini@redhat.com \
--cc=quic_mojha@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tycho@tycho.pizza \
--cc=zwisler@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox