From: Namhyung Kim <namhyung@kernel.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: <linux-kernel@vger.kernel.org>,
acme@ghostprotocols.net, a.p.zijlstra@chello.nl,
jolsa@redhat.com
Subject: Re: [PATCH v2 1/2] perf tools: Add support for pinned modifier
Date: Wed, 07 Aug 2013 15:18:06 +0900 [thread overview]
Message-ID: <87bo5ayqg1.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1375795686-4226-1-git-send-email-michael@ellerman.id.au> (Michael Ellerman's message of "Tue, 6 Aug 2013 23:28:05 +1000")
Hi Michael,
On Tue, 6 Aug 2013 23:28:05 +1000, Michael Ellerman wrote:
> This commit adds support for a new modifier "D", which requests that the
> event, or group of events, be pinned to the PMU.
>
> The "p" modifier is already taken for precise, and "P" may be used in
> future to mean "fully precise".
>
> So we use "D", which stands for pinneD - and looks like a padlock, or if
> you're using the ":D" syntax perf smiles at you.
>
> This is an oft-requested feature from our HW folks, who want to be able
> to run a large number of events, but also want 100% accurate results for
> instructions per cycle.
>
> Comparison of results with and without pinning:
>
> $ perf stat -e '{cycles,instructions}:D' -e cycles,instructions,...
>
> 79,590,480,683 cycles # 0.000 GHz
> 166,123,716,524 instructions # 2.09 insns per cycle
> # 0.11 stalled cycles per insn
>
> 79,352,134,463 cycles # 0.000 GHz [11.11%]
> 165,178,301,818 instructions # 2.08 insns per cycle
> # 0.11 stalled cycles per insn [11.13%]
>
> As you can see although perf does a very good job of scaling the values
> in the non-pinned case, there is some small discrepancy.
>
> The patch is fairly straight forward, the one detail is that we need to
> make sure we only request pinning for the group leader when we have a
> group.
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
next prev parent reply other threads:[~2013-08-07 6:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:28 Michael Ellerman
2013-08-06 13:28 ` [PATCH v2 2/2] perf tests: Add tests of new " Michael Ellerman
2013-08-06 13:59 ` Jiri Olsa
2013-08-07 6:18 ` Namhyung Kim
2013-08-12 10:24 ` [tip:perf/core] " tip-bot for Michael Ellerman
2013-08-06 13:59 ` [PATCH v2 1/2] perf tools: Add support for " Jiri Olsa
2013-08-07 5:19 ` Michael Ellerman
2013-08-07 20:16 ` Arnaldo Carvalho de Melo
2013-08-07 21:33 ` Michael Ellerman
2013-08-06 14:02 ` Jiri Olsa
2013-08-07 6:18 ` Namhyung Kim [this message]
2013-08-12 10:23 ` [tip:perf/core] " tip-bot for Michael Ellerman
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=87bo5ayqg1.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
/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
all inboxes | Powered by JetHome®