All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Steven Rostedt <rostedt@goodmis.org>
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 11:10:43 -0400	[thread overview]
Message-ID: <699bcae748cbb9663029542f93c9c83bc8a2c029.camel@HansenPartnership.com> (raw)
In-Reply-To: <20250715105041.6f63f4a5@batman.local.home>

On Tue, 2025-07-15 at 10:50 -0400, Steven Rostedt wrote:
> On Tue, 15 Jul 2025 10:38:34 -0400
> James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> 
> > > Well, if you can get those cloud people to invest in that work
> > > without causing any regressions, go for it.  
> > 
> > I think you know as well as I no investment happens without some
> > indication of upstream being in favour, particularly for large
> > changes.
> 
> I think you just pointed out why Mathieu doesn't want to do this huge
> update to merge upstream.

I didn't say he would ... I said you might be able to persuade the
cloud companies to do it.  That's not to say he (and you) couldn't help
incentivise them that their investment might pay off.

> > So they're not going to invest in doing this on spec because it
> > would be unmaintainable out of tree and would be way more hassle
> > than simply having customers reboot as they do today.
> > 
> > > 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().  
> > 
> > I don't believe I said that: purpose is not monolithic in open
> > source
> 
> No you didn't say that, but I figured I'd mention it as it was likely
> a thought someone may have had when reading your reply ;-)
> 
> > because people do things for wildly different reasons which a
> > clever leader can stitch together into something more
> > synergistically useful. The cloud vendors would be invested solely
> > for the purpose of being able to load tracing infrastructure on
> > demand (with the permission of the tenant) into a running kernel. 
> > They wouldn't care at all about the symbol export problems of
> > LTTng.  However, working with the cloud vendors on what they want
> > (and could be persuaded to invest in) would give you what you
> > wanted: an in-tree consumer for these symbols.
> 
> I have no vested interest in it. Mathieu has just been very helpful
> for the last several years with reviewing and improving the in-tree
> tracing infrastructure (which LTTng received no benefit from), that
> I'm just paying back the favor in trying to help him out.

Well, if you've no interest in thinking outside the box, by all means
continue banging your head against it until you think your payback has
been achieved ...  I'll go and get the popcorn.

Regards,

James


  reply	other threads:[~2025-07-15 15:10 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 [this message]
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=699bcae748cbb9663029542f93c9c83bc8a2c029.camel@HansenPartnership.com \
    --to=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@goodmis.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.