From: Steven Rostedt <rostedt@goodmis.org>
To: Ross Zwisler <zwisler@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ross Zwisler <zwisler@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Hao Luo <haoluo@google.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Jiri Olsa <jolsa@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>, Leon Romanovsky <leon@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Martin KaFai Lau <martin.lau@linux.dev>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mykola Lysenko <mykolal@fb.com>, Shuah Khan <shuah@kernel.org>,
Song Liu <song@kernel.org>, Stanislav Fomichev <sdf@google.com>,
Yonghong Song <yhs@fb.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH bpf-next v4 2/2] selftests/bpf: use canonical ftrace path
Date: Mon, 13 Mar 2023 18:39:46 -0400 [thread overview]
Message-ID: <20230313183946.1a98ef01@gandalf.local.home> (raw)
In-Reply-To: <20230313205628.1058720-3-zwisler@kernel.org>
On Mon, 13 Mar 2023 14:56:28 -0600
Ross Zwisler <zwisler@kernel.org> wrote:
> 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
>
> Many tests in the bpf selftest code still refer to this older debugfs
> path, so let's update them to avoid confusion.
>
> Signed-off-by: Ross Zwisler <zwisler@google.com>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> ---
> tools/testing/selftests/bpf/get_cgroup_id_user.c | 9 +++++++--
> .../selftests/bpf/prog_tests/kprobe_multi_test.c | 7 ++++++-
> .../selftests/bpf/prog_tests/task_fd_query_tp.c | 9 +++++++--
> .../selftests/bpf/prog_tests/tp_attach_query.c | 9 +++++++--
> .../testing/selftests/bpf/prog_tests/trace_printk.c | 10 +++++++---
> .../selftests/bpf/prog_tests/trace_vprintk.c | 10 +++++++---
> .../selftests/bpf/progs/test_stacktrace_map.c | 2 +-
> tools/testing/selftests/bpf/progs/test_tracepoint.c | 2 +-
> tools/testing/selftests/bpf/test_ftrace.sh | 7 ++++++-
> tools/testing/selftests/bpf/test_tunnel.sh | 13 +++++++++----
> tools/testing/selftests/bpf/trace_helpers.c | 8 ++++++--
> 11 files changed, 64 insertions(+), 22 deletions(-)
next prev parent reply other threads:[~2023-03-13 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230310192050.4096886-1-zwisler@kernel.org>
2023-03-13 20:56 ` [PATCH bpf-next v4 0/2] use canonical ftrace path whenever possible Ross Zwisler
2023-03-13 20:56 ` [PATCH bpf-next v4 1/2] bpf: use canonical ftrace path Ross Zwisler
2023-03-14 5:10 ` patchwork-bot+netdevbpf
2023-03-13 20:56 ` [PATCH bpf-next v4 2/2] selftests/bpf: " Ross Zwisler
2023-03-13 22:39 ` Steven Rostedt [this message]
2023-03-13 21:00 ` [PATCH bpf-next v4 0/2] use canonical ftrace path whenever possible Ross Zwisler
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=20230313183946.1a98ef01@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=jgg@ziepe.ca \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=mst@redhat.com \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=zwisler@google.com \
--cc=zwisler@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).