lkml.org 
[lkml]   [2006]   [Sep]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

* Roman Zippel <zippel@linux-m68k.org> wrote:

> Since my options are right now limited to a static tracer in first
> place, [...]

Lets see the equation of the current situation. On one side you want
static tracing but you dont want to implement kprobes on m68k - although
you probably could. On the other side there is the main kernel, which,
if it ever accepted static tracepoints, could probably never get rid of
them.

so, you request the main kernel to accept hundreds of static tracepoints
that would probably never go away, just because you are reluctant at the
moment to implement kprobes? And that only to bridge a temporary period
of time when m68k has no kprobes support yet? Combined with the fact
that m68k was just fine without tracing for 13 years? Did i get that
right?

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-09-17 01:11    [from the cache]
©2003-2011 Jasper Spaans