Re: [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17

[Mathieu Desnoyers]

* Frank Ch. Eigler (fche@xxxxxxxxxx) 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/