Re: [PATCH 2/2] perf: Walk through the relevant events only

From: Peter Zijlstra
Date: Fri Mar 05 2010 - 12:39:21 EST

On Fri, 2010-03-05 at 18:33 +0100, Frederic Weisbecker wrote:
> On Fri, Mar 05, 2010 at 06:20:29PM +0100, Peter Zijlstra wrote:
> > On Fri, 2010-03-05 at 18:03 +0100, Frederic Weisbecker wrote:
> > >
> > > Now isn't the problem more in the fact that most of the swevents
> > > should be tracepoints?
> >
> > No, different interface, and I don't want to require TRACE=y, I already
> > utterly hate that x86 requires PERF=y.
> >
> This could be reduced to the strict minimum, say CONFIG_TRACEPOINT
> and some code around just to support the event ids.

Can't, software events already are an ABI so we'll have to support that
forever, but sure you can make something that reduces to the current
software event callback on TRACE=n and maps to the right software event
id when TRACE=y.

> Software events could be made optionals too.

Sure, but they're nowhere near as much code as tracepoints.

> > I already
> > utterly hate that x86 requires PERF=y.
> Me too, and it's my bad, so me double too. Sometimes I think
> we should make BREAKPOINTs optional, default y. I just don't know
> if something like this that has always been builtin can be made
> optional.

Simply for build testing that would be useful, we could make it an
embedded switch.

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