From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86, perf: Use INST_RETIRED.PREC_DIST for cycles:pp on Skylake
Date: Tue, 20 Oct 2015 13:36:08 +0200 [thread overview]
Message-ID: <20151020113608.GC17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1445295496-8550-1-git-send-email-andi@firstfloor.org>
On Mon, Oct 19, 2015 at 03:58:16PM -0700, Andi Kleen wrote:
> Switch the cycles:pp alias from UOPS_RETITRED to INST_RETIRED.PREC_DIST.
> The basic mechanism of abusing the inverse cmask to get all cycles
> works the same as before.
>
> PREC_DIST has special support for avoiding shadow effects, which
> can give better results compare to UOPS_RETIRED. The drawback is
> that PREC_DIST can only schedule on counter 1, but that is ok for
> cycle sampling, as there is normally no need to do multiple cycle
> sampling runs in parallel. It is still possible to run perf top
> in parallel, as that doesn't use precise mode. Also of course
> the multiplexing can still allow parallel operation.
So the worry I have with this is that there might indeed be people
wanting to use this in parallel.
Typically on workstations you do not, because there's only a single
user, but on servers it might be more common. The thing I expect to be
most common is having both a CPU wide and a per task cycle counter
enabled.
This means a fairly visible change in behaviour depending on uarch.
And you having killed the flag bits for PEBS events precludes people
from using this manually, right? I think we want to exempt .inv=1
.cmask=16 from that general rule on general utility value.
We could maybe abuse .precise_ip = 3 for this?
> On earlier parts there were various hardware bugs in it
> (but no show stopper on IvyBridge and up I believe),
> so it could be enabled there after sufficient testing.
Just enable it for IVB+ then.
> On Sandy Bridge PREC_DIST can only be scheduled as a single
> event on the PMU, which is too limiting. Before Sandy
> Bridge it was not supported.
Right, that was a bit cumbersome :-)
next prev parent reply other threads:[~2015-10-20 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 22:58 [PATCH] x86, perf: Use INST_RETIRED.PREC_DIST for cycles:pp on Skylake Andi Kleen
2015-10-20 11:36 ` Peter Zijlstra [this message]
2015-10-20 22:28 ` Andi Kleen
2015-10-21 8:09 ` Peter Zijlstra
2015-10-21 15:26 ` Andi Kleen
2015-10-21 16:52 ` Peter Zijlstra
2015-10-21 16:55 ` Andi Kleen
2015-10-21 18:57 ` Peter Zijlstra
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=20151020113608.GC17308@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).