Hi,
On Fri, 15 Sep 2006, Jes Sorensen wrote:
> Roman Zippel wrote:
> > The claim that these tracepoints would be maintainance burden is pretty
> > much unproven so far. The static tracepoint haters just assume the kernel
> > will be littered with thousands of unrelated tracepoints, where a good
> > tracepoint would only document what already happens in that function, so
> > that the tracepoint would be far from something obscure, which only few
> > people could understand and maintain.
>
> How do you propose to handle the case where two tracepoint clients wants
> slightly different data from the same function? I saw this with LTT
> users where someone wanted things in different places in schedule().
>
> It *is* a nightmare to maintain.
That nightmare would not be with tracepoints itself, but with the users of
it, so you're missing the point.
Tracepoints can be abused of course, but it's quite a leap to conclude
from this that they are bad in general.
> You still haven't explained your argument about kprobes not being
> generally available - where?
Huh? What kind of explanation do you want?
$ grep KPROBES arch/*/Kconf*
arch/i386/Kconfig:config KPROBES
arch/ia64/Kconfig:config KPROBES
arch/powerpc/Kconfig:config KPROBES
arch/sparc64/Kconfig:config KPROBES
arch/x86_64/Kconfig:config KPROBES
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
