From: Steven Rostedt <rostedt@goodmis.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@infradead.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] LTTng upstreaming next steps
Date: Tue, 15 Jul 2025 09:16:49 -0400 [thread overview]
Message-ID: <20250715091649.3cc933fa@gandalf.local.home> (raw)
In-Reply-To: <9f6700d1fb62da8ce633f755b0c9e2d5c2704825.camel@HansenPartnership.com>
On Tue, 15 Jul 2025 08:50:08 -0400
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> What's wrong with doing this the other way around? i.e. making ftrace
> and perf modules? That way you could legitimately export the symbol
> you're asking about and there would be way less out-of-tree
> disadvantage to LTTng? I know a lot of cloud people who would be
> really happy if the tracing infrastructure were modular because it
> would save us from having to boot different kernels to do in depth
> problem analysis for otherwise locked down environments, so they might
> be willing to invest in upstream development to help you achieve this.
Well, if you can get those cloud people to invest in that work without
causing any regressions, go for it.
But I doubt it would be acceptable to make the ftrace tracing
infrastructure into a module for the sole purpose of allowing LTTng to have
EXPORT_SYMBOL_GPL().
-- Steve
next prev parent reply other threads:[~2025-07-15 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 19:41 [RFC] LTTng upstreaming next steps Mathieu Desnoyers
2025-07-14 20:00 ` Linus Torvalds
2025-07-14 20:27 ` Steven Rostedt
2025-07-14 20:37 ` Steven Rostedt
2025-07-14 21:04 ` Linus Torvalds
2025-07-15 9:24 ` Steven Rostedt
2025-07-15 12:50 ` James Bottomley
2025-07-15 13:16 ` Steven Rostedt [this message]
2025-07-15 14:38 ` James Bottomley
2025-07-15 14:50 ` Steven Rostedt
2025-07-15 15:10 ` James Bottomley
2025-07-15 15:16 ` Steven Rostedt
2025-07-15 15:13 ` Steven Rostedt
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=20250715091649.3cc933fa@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).