mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Theodore Tso <tytso@mit.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Christoph Hellwig <hch@infradead.org>,
	ltt-dev@lists.casi.polymtl.ca, Zhaolei <zhaolei@cn.fujitsu.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: LTTng kernel integration roadmap, update
Date: Tue, 25 Nov 2008 20:30:17 +0100	[thread overview]
Message-ID: <20081125193017.GA6550@uranus.ravnborg.org> (raw)
In-Reply-To: <20081125175937.GA525@mit.edu>

On Tue, Nov 25, 2008 at 12:59:37PM -0500, Theodore Tso wrote:
> On Tue, Nov 25, 2008 at 04:40:11PM +0100, Sam Ravnborg wrote:
> > > 
> > > Mathieu, if you're feeling keen I'd suggest that you just type `mkdir
> > > -p userspace/lttng' and build your userspace tools in there.
> > 
> > Maybe this can help...
> > 
> > 	Sam
> > 
> > diff --git a/usr/lttng/Makefile b/usr/lttng/Makefile
> > new file mode 100644
> > index 0000000..8667998
> > --- /dev/null
> > +++ b/usr/lttng/Makefile
> > @@ -0,0 +1,4 @@
> > +
> > +always := ltt
> > +
> > +hostprogs-y := ltt
> 
> hostprogs are intended to be run on the host during the compilation
> process, right?  What we really want is something that allows us to
> build userspace programs intended for use on the target, not the host,
> since they aren't going to be used when the system is compiled, but
> when the system is run.

Yes. And if this fly I will add support for that.
The majority build their kernel on the same host where they run it,
or at least a binary compatible host.

> 
> This also brings up some interesting questions such as where would we
> install these userspace programs (which could be kernel version
> specific), and how they would be packaged.
We already have similar userspace tools which we have no problem distributing.
Think of checkpatch, bloat-o-meter, cleanfile etc.

They happens to be scripts and not binaries. But otherwise I 
see no big difference.

	Sam

  parent reply	other threads:[~2008-11-25 19:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 11:28 Mathieu Desnoyers
2008-11-24 11:41 ` Christoph Hellwig
2008-11-24 12:20   ` Mathieu Desnoyers
2008-11-24 16:58     ` Steven Rostedt
2008-11-24 20:46       ` [ltt-dev] " Mathieu Desnoyers
2008-11-25  7:09         ` Mathieu Desnoyers
2008-11-25 13:57       ` Andrew Morton
2008-11-25 15:40         ` Sam Ravnborg
2008-11-25 17:59           ` Theodore Tso
2008-11-25 19:09             ` Andrew Morton
2008-11-25 19:30             ` Sam Ravnborg [this message]
2008-11-28 12:56           ` [ltt-dev] " Mathieu Desnoyers
2008-11-28 12:58         ` Mathieu Desnoyers
2008-11-25  8:24     ` Christoph Hellwig
2008-11-25  8:47       ` [ltt-dev] " Mathieu Desnoyers
2008-11-25  8:57       ` Theodore Tso
2008-11-25  8:59         ` Christoph Hellwig
2008-12-04  3:49 ` Lai Jiangshan

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=20081125193017.GA6550@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=zhaolei@cn.fujitsu.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

Powered by JetHome