From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, fweisbec@gmail.com
Subject: Re: [PATCH] perf: remove sw events from multiplexing rotation list
Date: Thu, 06 Sep 2012 18:01:56 +0200 [thread overview]
Message-ID: <1346947316.18408.36.camel@twins> (raw)
In-Reply-To: <20120906132346.GA32717@quad>
On Thu, 2012-09-06 at 15:23 +0200, Stephane Eranian wrote:
> Software events (sw,tracepoints,...) do not need to be
> multiplexed. However, when using a SW event, the SW PMU
> (TYPE_SOFTWARE, TYPE_TRACEPOINT) was added to the per-cpu
> rotation_list. That list is used by perf_rotate_context()
> to iterate over all the PMUs to rotate event lists and
> multiplex.
>
> This is not needed for SW events. Doing this adds some
> unnecessary overhead, so drop it by rejecting SW PMUs
> in perf_pmu_rotate_start().
Thanks!
prev parent reply other threads:[~2012-09-06 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 13:23 [PATCH] perf: remove sw events from multiplexing rotation list Stephane Eranian
2012-09-06 16:01 ` Peter Zijlstra [this message]
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=1346947316.18408.36.camel@twins \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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