From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sam@smtp.polymtl.ca, Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
ltt-dev@lists.casi.polymtl.ca, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ltt-dev] LTTng kernel integration roadmap, update
Date: Fri, 28 Nov 2008 07:58:09 -0500 [thread overview]
Message-ID: <20081128125809.GB10401@Krystal> (raw)
In-Reply-To: <20081125055744.c3377164.akpm@linux-foundation.org>
* Andrew Morton (akpm@linux-foundation.org) wrote:
> On Mon, 24 Nov 2008 11:58:40 -0500 (EST) Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > > The question that prevails is therefore : should we ship userspace
> > > binary with the kernel tree at all ? And if yes, how should the resuting
> > > executables be packaged and deployed ? Should it be installed in the
> > > system along with kernel modules or should it be populated into a
> > > filesystem populated by kernelspace ?
> > >
> > > Or is it better to do as we have always done and keep the userspace
> > > tools separated from the kernel tree ?
> >
> > I say keep the user space tools separate as much as possible.
>
> So... we're now planning to build even more userspace tools into the
> kernel merely because we don't know how to deliver userspace tools in
> userspace?
>
> Worse, those kernel-based userspace tools will simply be presenting a
> textual form of something which the kernel already makes available in a
> binary form?
>
> This is so lame.
>
> Any proposal to fix all this will result in vast amounts of
> inconclusive chin-scratching again. Last time this came up, we ended
> up with the old impractical put-it-in-util-linux chestnut. I think the
> time has come for us to admit that this isn't working out.
>
> Mathieu, if you're feeling keen I'd suggest that you just type `mkdir
> -p userspace/lttng' and build your userspace tools in there. One they
> are there and real, the issues around versioning, installation and
> delivery will still need tobe sorted out, but we need to start
> somewhere.
>
Yes, I like the idea of having a kernel-developer oriented version of
the userspace tools, which may not have packaging requirements as strong
as standard userspace packages. Just keeping them around with the kernel
build tree would be a good start, and we could probably go as far as
installing them along with the kernel modules in /lib/modules/`uname
-r`.
Mathieu
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-11-28 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 11:28 LTTng kernel integration roadmap, update 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
2008-11-28 12:56 ` [ltt-dev] " Mathieu Desnoyers
2008-11-28 12:58 ` Mathieu Desnoyers [this message]
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=20081128125809.GB10401@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=Sam@smtp.polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.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).