[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1193766594.9068.48.camel@taijtu>
Date: Tue, 30 Oct 2007 18:49:54 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Jeff Garzik <jeff@...zik.org>, Randy Dunlap <rdunlap@...otime.net>,
hch@...radead.org, linux-kernel@...r.kernel.org,
Sam Ravnborg <sam@...nborg.org>,
Jens Axboe <jens.axboe@...cle.com>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Ingo Molnar <mingo@...hat.com>,
Philippe Elie <phil.el@...adoo.fr>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"William L. Irwin" <wli@...omorphy.com>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Lameter <christoph@...eter.com>,
Valdis.Kletnieks@...edu
Subject: Re: [RFC] Create kinst/ or ki/ directory ?
On Tue, 2007-10-30 at 13:24 -0400, Mathieu Desnoyers wrote:
> * Jeff Garzik (jeff@...zik.org) wrote:
> ...
> > Pick a shorter word like probes or profile or what... or better yet...
> > just leave most things in their current directories.
> ...
>
>
> How about something along the
>
> kinst or ki
>
> lines ?
>
> (for "kernel instrumentation")
I think I'm with jgarzik on this, lets not do this until its clear where
the generalized instrumentation goes to.
That is, i386/x86_64 -> x86 was part of a full integration plan, one
that was immediately followed up by a series of integration patches.
With this, I see no such plan. Please draft this generic instrumentation
you talk about, if after that we all like it, we can go moving files
together with the immediate purpose of integrating them.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists