public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Christoph Hellwig <hch@infradead.org>,
	Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
	Tom Zanussi <tzanussi@gmail.com>,
	karim@opersys.com, Michel Dagenais <michel.dagenais@polymtl.ca>,
	ltt-dev@lists.casi.polymtl.ca,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Robert Wisniewski <bob@watson.ibm.com>
Subject: Re: Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+
Date: Wed, 24 Jun 2009 10:23:26 -0700	[thread overview]
Message-ID: <20090624172326.GJ6779@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090624164909.GA20653@Krystal>

On Wed, Jun 24, 2009 at 12:49:09PM -0400, Mathieu Desnoyers wrote:
> * Frank Ch. Eigler (fche@redhat.com) wrote:
> > Mathieu Desnoyers <compudj@krystal.dyndns.org> writes:
> > 
> > > [...]  The goal we pursue by dual-licensing with GPLv2/LGPLv2.1 is
> > > to permit instrumented applications to be themselves distributed
> > > under other license than GPL. [...]
> > 
> > Is there some reason you can't just fork/copy off some earlier version
> > of these files over which you had sole authorship (if any)?
> > 
> 
> Actually, for LTTng, I own the copyright of almost everything we need.
> Most files written by others are mainly the debugfs interfaces done by
> Fujitsu. There is some derived work from RelayFS in
> ltt/ltt-relay-alloc.c and include/linux/ltt-relay.h, where getting IBM's
> approval would be good, but I think in the end this will end up being
> only a few tens of lines.

It is going to be a -lot- easier and faster to simply rewrite a few tens
of lines than to get any kind of approval.  ;-)

I cannot reasonably argue that the prior approval for RCU covers tracing,
sad to say.  So unless there is something very special about the few
tens of lines, could you please look at just clean-room rewriting them?

							Thanx, Paul

> > > [...]The goal is to permit this library, which includes the
> > > tracepoints, markers and LTTng features, to be used by userspace
> > > applications and libraries so they can add static instrumentation
> > > (as we currently do in the kernel). [...]
> > 
> > Just in case you're not aware, some API prior art for this is the
> > dtrace sdt.h widget (already supported by systemtap), and of course
> > it has no similarity to the various kernel tracing APIs.
> 
> Yep, we're aware of this. However, last time I checked, dtrace SDT used
> a breakpoint even for their userspace tracing, which has a way too large
> performance overhead for our needs.
> 
> Moreover, they support only very, very limited typing (0 to 5 u32). In
> this respect, tracepoints and markers are much more flexible.
> 
> Thanks,
> 
> Mathieu
> 
> > 
> > - FChE
> > 
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2009-06-24 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A412702.80707@polymtl.ca>
     [not found] ` <20090623191128.GA19010@Krystal>
     [not found]   ` <20090623191513.GA20253@Krystal>
2009-06-24  0:43     ` Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+ Mathieu Desnoyers
2009-06-24  8:33       ` Ingo Molnar
2009-06-24 14:14         ` Mathieu Desnoyers
2009-06-24 16:33           ` Frank Ch. Eigler
2009-06-24 16:49             ` Mathieu Desnoyers
2009-06-24 17:23               ` Paul E. McKenney [this message]
2009-06-29 23:00               ` Mark Wielaard

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=20090624172326.GJ6779@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bob@watson.ibm.com \
    --cc=compudj@krystal.dyndns.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=karim@opersys.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=michel.dagenais@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=pierre-marc.fournier@polymtl.ca \
    --cc=rostedt@goodmis.org \
    --cc=tzanussi@gmail.com \
    /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