[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1285176629.2275.1033.camel@laptop>
Date: Wed, 22 Sep 2010 19:30:29 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Jean Pihet <jean.pihet@...oldbits.com>,
Thomas Renninger <trenn@...e.de>, Ingo Molnar <mingo@...e.hu>,
Len Brown <len.brown@...el.com>, arjan@...radead.org,
Kevin Hilman <khilman@...prootsystems.com>,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
linux-omap@...r.kernel.org, linux-perf-users@...r.kernel.org,
linux-trace-users@...r.kernel.org
Subject: Re: [PATCH] tracing, perf: add more power related events
On Wed, 2010-09-22 at 10:06 -0700, Arjan van de Ven wrote:
> In this case we're talking about basically a suprious rename of
> something that isn't really an improvement
> (because it makes it harder to subscribe to only one type of event)...
> that's not a good thing.
People have been talking about more/more comprehensive power tracepoints
for a while, and I think that's a valid goal, if its really a rename I'm
sure you can work it out.
That said, I really didn't read this discussion much, but your stance
seems to be that any tracepoint you use must stay valid, and I object to
that.
What will do you do when we include a new scheduling policy and all the
scheduler tracepoints need to change? (yes that's really going to
happen)
I'm not going to carry double tracepoints, and I'm not going to not
merge that policy.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists