From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Jeff Garzik <jeff@garzik.org>,
Randy Dunlap <rdunlap@xenotime.net>,
hch@infradead.org, linux-kernel@vger.kernel.org,
Sam Ravnborg <sam@ravnborg.org>,
Jens Axboe <jens.axboe@oracle.com>,
Prasanna S Panchamukhi <prasanna@in.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@redhat.com>,
Philippe Elie <phil.el@wanadoo.fr>,
Linus Torvalds <torvalds@linux-foundation.org>,
"William L. Irwin" <wli@holomorphy.com>,
Arjan van de Ven <arjan@infradead.org>,
Christoph Lameter <christoph@lameter.com>,
Valdis.Kletnieks@vt.edu
Subject: Re: [RFC] Create kinst/ or ki/ directory ?
Date: Tue, 30 Oct 2007 18:49:54 +0100 [thread overview]
Message-ID: <1193766594.9068.48.camel@taijtu> (raw)
In-Reply-To: <20071030172442.GA4477@Krystal>
On Tue, 2007-10-30 at 13:24 -0400, Mathieu Desnoyers wrote:
> * Jeff Garzik (jeff@garzik.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.
next prev parent reply other threads:[~2007-10-30 17:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:51 [RFC] Create instrumentation directory (git repository) Mathieu Desnoyers
2007-10-29 22:47 ` Randy Dunlap
2007-10-29 22:54 ` Jeff Garzik
2007-10-29 23:04 ` Mathieu Desnoyers
2007-10-29 23:08 ` Jeff Garzik
2007-10-29 23:35 ` Mathieu Desnoyers
2007-10-30 0:47 ` Jeff Garzik
2007-10-30 1:38 ` Mathieu Desnoyers
2007-10-30 9:13 ` Arnaldo Carvalho de Melo
2007-10-30 17:24 ` [RFC] Create kinst/ or ki/ directory ? Mathieu Desnoyers
2007-10-30 17:49 ` Peter Zijlstra [this message]
2007-10-30 17:50 ` Linus Torvalds
2007-10-30 17:58 ` Christoph Hellwig
2007-10-30 18:56 ` Mathieu Desnoyers
2007-10-30 19:25 ` Linus Torvalds
2007-10-30 20:40 ` Mathieu Desnoyers
2007-10-31 15:48 ` Frank Ch. Eigler
2007-10-31 16:29 ` Arjan van de Ven
2007-10-31 19:05 ` Frank Ch. Eigler
2007-10-31 19:49 ` Arjan van de Ven
2007-10-31 16:36 ` Mathieu Desnoyers
2007-10-31 19:29 ` Frank Ch. Eigler
2007-10-30 21:46 ` Sam Ravnborg
2007-10-29 23:20 ` [RFC] Create instrumentation directory (git repository) Christoph Lameter
2007-10-29 23:40 ` Mathieu Desnoyers
2007-10-29 23:45 ` Christoph Lameter
2007-10-30 0:51 ` Jeff Garzik
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=1193766594.9068.48.camel@taijtu \
--to=a.p.zijlstra@chello.nl \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=arjan@infradead.org \
--cc=christoph@lameter.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@redhat.com \
--cc=phil.el@wanadoo.fr \
--cc=prasanna@in.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®