Re: [PATCH] Linux Kernel Markers

[Ingo Molnar]

* Ingo Molnar <mingo@xxxxxxx> wrote:

> > +choice
> > +	prompt "MARK code marker behavior"
> 
> > +config MARK_KPROBE
> > +config MARK_JPROBE
> > +config MARK_FPROBE
> > +	Change markers for a function call.
> > +config MARK_PRINT
> 
> as indicated before in great detail, NACK on this profileration of 
> marker options, especially the function call one. I'd like to see _one_ 
> marker mechanism that distros could enable, preferably with zero (or at 
> most one NOP) in-code overhead. (You can of course patch whatever 
> extension ontop of it, in out-of-tree code, to gain further performance 
> advantage by generating direct system-calls.)
                                    ^---function

	Ingo
-
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/