From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: Basic perf PMU support for Haswell v12
Date: Thu, 30 May 2013 09:01:49 +0200 [thread overview]
Message-ID: <20130530070149.GA10409@gmail.com> (raw)
In-Reply-To: <20130530063529.GB5310@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> * Andi Kleen <andi@firstfloor.org> wrote:
>
> > On Tue, May 28, 2013 at 08:29:15AM +0200, Ingo Molnar wrote:
> > >
> > > * Andi Kleen <andi@firstfloor.org> wrote:
> > >
> > > > All outstanding issues fixed I hope. And I added mem-loads/stores support.
> > > >
> > > > Contains support for:
> > > > - Basic Haswell PMU and PEBS support
> > > > - Late unmasking of the PMI
> > > > - mem-loads/stores support
> > > >
> > > > v2: Addressed Stephane's feedback. See individual patches for details.
> > > > v3: now even more bite-sized. Qualifier constraints merged earlier.
> > > > v4: Rename some variables, add some comments and other minor changes.
> > > > Add some Reviewed/Tested-bys.
> > > > v5: Address some minor review feedback. Port to latest perf/core
> > > > v6: Add just some variable names, add comments, edit descriptions, some
> > > > more testing, rebased to latest perf/core
> > > > v7: Expand comment
> > > > v8: Rename structure field.
> > > > v9: No wide counters, but add basic LBRs. Add some more
> > > > constraints. Rebase to 3.9rc1
> > > > v10: Change some whitespace. Rebase to 3.9rc3
> > > > v11: Rebase to perf/core. Fix extra regs. Rename INTX.
> > > > v12: Rebase to 3.10-rc2
> > > > Add mem-loads/stores support for parity with Sandy Bridge.
> > > > Fix fixed counters (Thanks Ingo!)
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > > Make late ack optional
> > > > Export new config bits in sysfs.
> > > > Minor changes
> > >
> > > I reported a pretty nasty regression with the previous version (v10) which
> > > made this series break default 'perf top' on non-Haswell systems - but
> > > it's unclear from this changelog to what extent you managed to reproduce
> > > the bug and fix it, and what the fix was?
> >
> > Thanks for checking.
> > I didn't reproduce it, but I found a problem by code review with the
> > fixed counter constraints.
> >
> > I think I fixed it by adding this hunk:
> >
> > @@ -2227,7 +2313,7 @@ __init int intel_pmu_init(void)
> > * counter, so do not extend mask to generic counters
> > */
> > for_each_event_constraint(c, x86_pmu.event_constraints) {
> > - if (c->cmask != X86_RAW_EVENT_MASK
> > + if (c->cmask != FIXED_EVENT_FLAGS
> > || c->idxmsk64 == INTEL_PMC_MSK_FIXED_REF_CYCLES) {
> > continue;
> > }
> >
> > It would be cleaner to detect the fixed counters in some other way,
> > but that was the simplest fix I could find.
> >
> > Testing appreciated
>
> Fair enough - I'll give it a whirl - that hunk does indeed look like it
> could make a difference.
Ok, I can confirm that this fixed the perf top and perf record regression
I saw on Intel systems.
Thanks,
Ingo
next prev parent reply other threads:[~2013-05-30 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1369261073-1275-1-git-send-email-andi@firstfloor.org>
2013-05-28 6:29 ` Basic perf PMU support for Haswell v12 Ingo Molnar
2013-05-28 16:20 ` Andi Kleen
2013-05-30 6:35 ` Ingo Molnar
2013-05-30 7:01 ` Ingo Molnar [this message]
[not found] ` <1369261073-1275-5-git-send-email-andi@firstfloor.org>
2013-05-30 6:43 ` [PATCH 4/6] perf, x86: Move NMI clearing to end of PMI handler v2 Ingo Molnar
2013-05-30 7:22 ` Basic perf PMU support for Haswell v12 Ingo Molnar
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=20130530070149.GA10409@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).