From: Stephane Eranian <eranian@google.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
jmario@redhat.com, dzickus@redhat.com, jolsa@redhat.com,
acme@redhat.com
Subject: [PATCH 0/2] perf/x86: improve Intel load latency and precise store event constraints
Date: Thu, 19 Jun 2014 17:58:27 +0200 [thread overview]
Message-ID: <1403193509-22393-1-git-send-email-eranian@google.com> (raw)
This short series of patches improves the event contraint
tables for Intel SNB, IVB and HSW processors.
1/ removes unnecessary constraints on the Load Latency event
The constraint to counter 3 is not needed. The events works
well on any PEBS-capable counter. The artificial constraint on
counter 3, was used to simplify event scheduling because the
event uses an extra MSR which is ahred by all the counters.
But perf_events can managed shared regs without artificial
counter constraints.
2/ remove unecessary constraint on precise store on HSW
On SNB,IVB, the precise store event has to be on counter 3.
On HSW, precise store is not implemented the same way and
can use any counter. Thus we lift the constraint on all
precise store events on HSW.
The advantage of this series is that it allows capturing load
latency and precise store events at the same time without
multiplexing.
Stephane Eranian (2):
perf/x86: update Haswell PEBS event constraints
perf/x86: fix constraint for load latency and precise store event
arch/x86/kernel/cpu/perf_event_intel.c | 2 --
arch/x86/kernel/cpu/perf_event_intel_ds.c | 22 ++++++++--------------
2 files changed, 8 insertions(+), 16 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-06-19 15:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 15:58 Stephane Eranian [this message]
2014-06-19 15:58 ` [PATCH 1/2] perf/x86: update Haswell PEBS " Stephane Eranian
2014-06-19 18:00 ` Andi Kleen
2014-06-19 19:53 ` Stephane Eranian
2014-06-19 20:18 ` Andi Kleen
2014-06-19 20:31 ` Stephane Eranian
2014-06-19 20:40 ` Andi Kleen
2014-06-19 20:45 ` Stephane Eranian
2014-06-20 13:44 ` Stephane Eranian
2014-06-23 7:35 ` Peter Zijlstra
2014-06-23 14:16 ` Andi Kleen
2014-06-23 7:14 ` Peter Zijlstra
2014-06-23 8:06 ` Stephane Eranian
2014-06-23 11:37 ` Peter Zijlstra
2014-06-23 11:51 ` Stephane Eranian
2014-06-23 15:47 ` Andi Kleen
2014-06-23 7:12 ` Peter Zijlstra
2014-06-19 15:58 ` [PATCH 2/2] perf/x86: fix constraints for load latency and precise events Stephane Eranian
2014-06-19 20:56 ` Andi Kleen
2014-06-23 8:42 ` Peter Zijlstra
2014-06-23 9:00 ` Stephane Eranian
2014-06-23 11:39 ` Peter Zijlstra
2014-06-23 14:22 ` Andi Kleen
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=1403193509-22393-1-git-send-email-eranian@google.com \
--to=eranian@google.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=dzickus@redhat.com \
--cc=jmario@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®