From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Paul Mackerras <paulus@samba.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@redhat.com>,
Jason Baron <jbaron@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 2/2] perf: Walk through the relevant events only
Date: Fri, 5 Mar 2010 18:33:46 +0100 [thread overview]
Message-ID: <20100305173342.GE5244@nowhere> (raw)
In-Reply-To: <1267809629.4942.0.camel@laptop>
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.
Software events could be made optionals too.
I just don't like this multiplication of probe points of different
natures in a single point. That's wasteful.
> 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.
next prev parent reply other threads:[~2010-03-05 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 7:00 [PATCH 1/2] perf: Drop the obsolete profile naming for trace events Frederic Weisbecker
2010-03-05 7:00 ` [PATCH 2/2] perf: Walk through the relevant events only Frederic Weisbecker
2010-03-05 9:39 ` Peter Zijlstra
2010-03-05 17:03 ` Frederic Weisbecker
2010-03-05 17:20 ` Peter Zijlstra
2010-03-05 17:33 ` Frederic Weisbecker [this message]
2010-03-05 17:39 ` Peter Zijlstra
2010-03-05 17:46 ` Frederic Weisbecker
2010-03-08 18:35 ` [RFC PATCH] perf: Store relevant events in a hlist Frederic Weisbecker
2010-03-10 19:34 ` Peter Zijlstra
2010-03-10 20:33 ` Frederic Weisbecker
2010-03-10 20:46 ` Peter Zijlstra
2010-03-10 21:04 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100305173342.GE5244@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox