From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Namhyung Kim <namhyung@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>
Subject: Re: [RFC][PATCH] tracing: Deprecate auto-mounting tracefs in debugfs
Date: Tue, 17 Jun 2025 19:41:07 +0200 [thread overview]
Message-ID: <20250617174107.GB1613376@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250617133614.24e2ba7f@gandalf.local.home>
On Tue, Jun 17, 2025 at 01:36:14PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> In January 2015, tracefs was created to allow access to the tracing
> infrastructure without needing to compile in debugfs. When tracefs is
> configured, the directory /sys/kernel/tracing will exist and tooling is
> expected to use that path to access the tracing infrastructure.
>
> To allow backward compatibility, when debugfs is mounted, it would
> automount tracefs in its "tracing" directory so that tooling that had hard
> coded /sys/kernel/debug/tracing would still work.
>
> It has been over 10 years since the new interface was introduced, and all
> tooling should now be using it. Start the process of deprecating the old
> path so that it doesn't need to be maintained anymore.
I've always used /debug/tracing/ (because /debug is the right place to
mount debugfs). You're saying this is going away and will break all my
scripts?!
next prev parent reply other threads:[~2025-06-17 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 17:36 [RFC][PATCH] tracing: Deprecate auto-mounting tracefs in debugfs Steven Rostedt
2025-06-17 17:41 ` Peter Zijlstra [this message]
2025-06-17 17:54 ` Steven Rostedt
2025-06-17 18:00 ` Peter Zijlstra
2025-06-17 18:48 ` Ian Rogers
2025-06-17 19:14 ` Steven Rostedt
2025-06-18 7:21 ` Sebastian Andrzej Siewior
2025-06-18 9:27 ` Peter Zijlstra
2025-06-17 19:29 ` Steven Rostedt
2025-06-18 9:18 ` Christian Brauner
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=20250617174107.GB1613376@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=brauner@kernel.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=jack@suse.cz \
--cc=jolsa@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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