All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	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>,
	Peter Zijlstra <pzijlstr@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>
Subject: Re: [RFC] Create instrumentation directory (git repository)
Date: Mon, 29 Oct 2007 18:54:18 -0400	[thread overview]
Message-ID: <4726649A.5020605@garzik.org> (raw)
In-Reply-To: <20071029154741.cb093f55.rdunlap@xenotime.net>

Randy Dunlap wrote:
> On Mon, 29 Oct 2007 17:51:38 -0400 Mathieu Desnoyers wrote:
> 
>> Hi,
>>
>> Since we already have the Instrumentation menu in
>> kernel/Kconfig.instrumentation and instrumentation code all over the
>> kernel tree:
>>
>> arch/*/oprofile/*.c
>> kernel/kprobes.c
>> arch/*/kernel/kprobes.c
>> kernel/marker.c
>> kernel/profile.c
>> kernel/lockdep.c
>> vm/vmstat.c
>> block/blktrace.c
>> drivers/base/power/trace.c
>>
>> We could move them to
>>
>> instrumentation/
>> arch/*/instrumentation/
>>
>> Therefore, we could also move the kprobes and marker samples under
>>
>> instrumentation/samples/
>>
>> Here is a link to a git repository containing the changes, based on
>> 2.6.24-rc1:
>>
>> git://ltt.polymtl.ca/linux-2.6-instrumentation.git instrumentation-for-linus
>> (the interesting range is : v2.6.24-rc1..instrumentation-for-linus)
>>
>> Through the gitweb interface:
>> http://ltt.polymtl.ca/cgi-bin/gitweb.cgi?p=linux-2.6-instrumentation.git
>>
>> Feedback is appreciated. Sorry for the huge CC list, but the change
>> involves many maintainers.
> 
> Two more added.  Jeff Garzik and Christoph H. sometimes have some comments
> about this.
> 
> It would be helpful if we could get comments on this in the next day
> or two [instead of in 1-2 weeks].

"instrumentation" is long, and painful to the fingers :)

	Jeff



  reply	other threads:[~2007-10-29 22:54 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 [this message]
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
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=4726649A.5020605@garzik.org \
    --to=jeff@garzik.org \
    --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=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=pzijlstr@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.