Re: [RFC] Create instrumentation directory (git repository)

2007-10-30 Thread Arnaldo Carvalho de Melo
Em Mon, Oct 29, 2007 at 07:35:15PM -0400, Mathieu Desnoyers escreveu: > I see no good reason to have so many different adhoc instrumentation > mechanisms for profiling (sched, vm, oprofile) and tracing (blktrace, > suspend/resume tracing) all over the place. Merging them in a single > directory see

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Mathieu Desnoyers
* Jeff Garzik ([EMAIL PROTECTED]) wrote: > Mathieu Desnoyers wrote: > >I see no good reason to have so many different adhoc instrumentation > >mechanisms for profiling (sched, vm, oprofile) and tracing (blktrace, > >suspend/resume tracing) all over the place. Merging them in a single > >directory s

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Jeff Garzik
Mathieu Desnoyers wrote: Putting stuff in instrumentation/ by no way means that it becomes optional for a subsystem, but merely that it could either export information useful for kernel instrumentation or have some infrastructure parts merged with others. More reason why you should not be movi

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Jeff Garzik
Mathieu Desnoyers wrote: I see no good reason to have so many different adhoc instrumentation mechanisms for profiling (sched, vm, oprofile) and tracing (blktrace, suspend/resume tracing) all over the place. Merging them in a single directory seems like a good step towards a more generic instrume

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Christoph Lameter
On Mon, 29 Oct 2007, Mathieu Desnoyers wrote: > * Christoph Lameter ([EMAIL PROTECTED]) wrote: > > On Mon, 29 Oct 2007, Mathieu Desnoyers wrote: > > > > > vm/vmstat.c > > > > The vm statistics are important for the operation of the VM. They are not > > optional. So I do not think that they fall

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Mathieu Desnoyers
* Jeff Garzik ([EMAIL PROTECTED]) wrote: > Mathieu Desnoyers wrote: > >* Jeff Garzik ([EMAIL PROTECTED]) wrote: > >>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/Kconfi

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Mathieu Desnoyers
* Christoph Lameter ([EMAIL PROTECTED]) wrote: > On Mon, 29 Oct 2007, Mathieu Desnoyers wrote: > > > vm/vmstat.c > > The vm statistics are important for the operation of the VM. They are not > optional. So I do not think that they fall under the category of > instrumentation. But I guess vm st

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Christoph Lameter
On Mon, 29 Oct 2007, Mathieu Desnoyers wrote: > vm/vmstat.c The vm statistics are important for the operation of the VM. They are not optional. So I do not think that they fall under the category of instrumentation. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in th

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Jeff Garzik
Mathieu Desnoyers wrote: * Jeff Garzik ([EMAIL PROTECTED]) wrote: 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/*/op

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Mathieu Desnoyers
* Jeff Garzik ([EMAIL PROTECTED]) wrote: > 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: > >> > >>arc

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Jeff Garzik
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

Re: [RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Randy Dunlap
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 > k

[RFC] Create instrumentation directory (git repository)

2007-10-29 Thread Mathieu Desnoyers
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/tr

Re: [RFC] create instrumentation/ directory

2007-10-25 Thread Valdis . Kletnieks
On Wed, 24 Oct 2007 13:31:02 EDT, Mathieu Desnoyers said: > Therefore, we could also move the kprobes and marker samples under > > instrumentation/samples/ > > My main concern is that 15 characters long directory name might be > inelegant (however, it only beats Documentation by 2). How so? i

Re: [RFC] create instrumentation/ directory

2007-10-24 Thread Randy Dunlap
On Wed, 24 Oct 2007 13:31:02 -0400 Mathieu Desnoyers wrote: > * Randy Dunlap ([EMAIL PROTECTED]) wrote: > > On Wed, 24 Oct 2007 09:19:05 -0400 Jeff Garzik wrote: > > > > > Honestly, I don't care at all about building the code. If that's what > > > you want, great. > > > > Yes, that is wanted.

[RFC] create instrumentation/ directory

2007-10-24 Thread Mathieu Desnoyers
* Randy Dunlap ([EMAIL PROTECTED]) wrote: > On Wed, 24 Oct 2007 09:19:05 -0400 Jeff Garzik wrote: > > > Honestly, I don't care at all about building the code. If that's what > > you want, great. > > Yes, that is wanted. They bitrot too easily -- not good. > > > My objection is more to adding