[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060919193623.GA9459@Krystal>
Date: Tue, 19 Sep 2006 15:36:24 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: linux-kernel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...l.org>, Ingo Molnar <mingo@...hat.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
Douglas Niehaus <niehaus@...s.ku.edu>,
Tom Zanussi <zanussi@...ibm.com>,
Paul Mundt <lethal@...ux-sh.org>, Jes Sorensen <jes@....com>,
Richard J Moore <richardj_moore@...ibm.com>,
William Cohen <wcohen@...hat.com>,
"Martin J. Bligh" <mbligh@...igh.org>,
Michel Dagenais <michel.dagenais@...ymtl.ca>,
systemtap@...rces.redhat.com, ltt-dev@...fik.org
Subject: Re: [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17
* Frank Ch. Eigler (fche@...hat.com) wrote:
> If you don't allow yourself to presume on-the-fly function
> recompilation, then these markers would need to be made run-time
> rather than compile-time configurable. That is, not like this:
>
> > +/* Menu configured markers */
> > +#ifndef CONFIG_MARK
> > +#define MARK MARK_INACTIVE
> > +#elif defined(CONFIG_MARK_PRINT)
> > +#define MARK MARK_PRINT
> > +#elif defined(CONFIG_MARK_FPROBE)
> > +#define MARK MARK_FPROBE
> > +#elif defined(CONFIG_MARK_KPROBE)
> > +#define MARK MARK_KPROBE
> > +#elif defined(CONFIG_MARK_JPROBE)
> > +#define MARK MARK_JPROBE
> > +#endif
By making them run-time configurable, I don't see any whay not to bloat the
kernel. How can be embed calls to printk+function+kprobe+djprobe without
having some kind of performance impact ?
Do you have any suggestion for this ? (or maybe am I missing your point ?)
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
-
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