From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 11:13:46 -0400 [thread overview]
Message-ID: <20250715111346.57587ec9@batman.local.home> (raw)
In-Reply-To: <20250715052459.0000e119@gandalf.local.home>
On Tue, 15 Jul 2025 05:24:59 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Either LTTng can use the same infrastructure as perf and ftrace, meaning it
> requires EXPORT_SYMBOL_GPL() on those interfaces, or it gets pulled in as
> is, so that it can incrementally start to share the code.
I believe that if we allowed LTTng to have access to the perf and
ftrace infrastructure, it would encourage more collaboration. It would
force Mathieu into working to get perf and ftrace and LTTng working
under one infrastructure so that it could finally get rid of its out of
tree module. Whereas, if we pulled it in as-is, there wouldn't be
really any incentive for it to change.
Now the question is, how do we allow LTTng's out of tree module to have
access to the internal infrastructure without breaking the
"EXPORT_SYMBOL_GPL() is only for in-tree modules" rule?
-- Steve
prev parent reply other threads:[~2025-07-15 15:13 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
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 [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=20250715111346.57587ec9@batman.local.home \
--to=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.