[lkml]   [2006]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Linux Kernel Markers

* Ingo Molnar <> 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.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-09-19 10:25    [W:0.158 / U:14.776 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site