From: Don Zickus <dzickus@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@ghostprotocols.net, jolsa@redhat.com,
jmario@redhat.com, ak@linux.intel.com
Subject: Re: [PATCH v2]: fix Haswell precise store data source encoding
Date: Thu, 15 May 2014 15:56:55 -0400 [thread overview]
Message-ID: <20140515195655.GG50500@redhat.com> (raw)
In-Reply-To: <20140515155644.GA3884@quad>
On Thu, May 15, 2014 at 05:56:44PM +0200, Stephane Eranian wrote:
>
> This patch fixes a bug in precise_store_data_hsw() whereby
> it would set the data source memory level to the wrong value.
>
> As per the the SDM Vol 3b Table 18-41 (Layout of Data Linear
> Address Information in PEBS Record), when status bit 0 is set
> this is a L1 hit, otherwise this is a L1 miss.
>
> This patch encodes the memory level according to the specification.
>
> In V2, we added the filtering on the store events.
> Only the following events produce L1 information:
> * MEM_UOPS_RETIRED.STLB_MISS_STORES
> * MEM_UOPS_RETIRED.LOCK_STORES
> * MEM_UOPS_RETIRED.SPLIT_STORES
> * MEM_UOPS_RETIRED.ALL_STORES
This worked great on our Haswell-EX box. I was a little surprised to find
out it did until I realized on Ivy Bridge 'mem-store' was a 0x02cd but on
Haswell it is now a 0x82d0. Go generic event types! :-)
Looking at the SDM documentation it does say something about
'UOPS_RETIRED.ALL' supporting stores too but can't find that event. Is
that a typo, much like the 0x02 umask for stores on the D0 event is
missing from the documentation? Just wanted to make sure we are not
missing one more case.
Thanks for the quick patch Stephane!
Tested-and-Reviewed-by: Don Zickus <dzickus@redhat.com>
>
> Signed-off-by: Stephane Eranian <eranian@google.com>
>
> diff --git a/arch/x86/kernel/cpu/perf_event_intel_ds.c b/arch/x86/kernel/cpu/perf_event_intel_ds.c
> index ae96cfa..980970c 100644
> --- a/arch/x86/kernel/cpu/perf_event_intel_ds.c
> +++ b/arch/x86/kernel/cpu/perf_event_intel_ds.c
> @@ -108,15 +108,31 @@ static u64 precise_store_data(u64 status)
> return val;
> }
>
> -static u64 precise_store_data_hsw(u64 status)
> +static u64 precise_store_data_hsw(struct perf_event *event, u64 status)
> {
> union perf_mem_data_src dse;
> + u64 cfg = event->hw.config & INTEL_ARCH_EVENT_MASK;
>
> dse.val = 0;
> dse.mem_op = PERF_MEM_OP_STORE;
> dse.mem_lvl = PERF_MEM_LVL_NA;
> +
> + /*
> + * L1 info only valid for following events:
> + *
> + * MEM_UOPS_RETIRED.STLB_MISS_STORES
> + * MEM_UOPS_RETIRED.LOCK_STORES
> + * MEM_UOPS_RETIRED.SPLIT_STORES
> + * MEM_UOPS_RETIRED.ALL_STORES
> + */
> + if (cfg != 0x12d0 && cfg != 0x22d0 && cfg != 0x42d0 && cfg != 0x82d0)
> + return dse.mem_lvl;
> +
> if (status & 1)
> - dse.mem_lvl = PERF_MEM_LVL_L1;
> + dse.mem_lvl = PERF_MEM_LVL_L1 | PERF_MEM_LVL_HIT;
> + else
> + dse.mem_lvl = PERF_MEM_LVL_L1 | PERF_MEM_LVL_MISS;
> +
> /* Nothing else supported. Sorry. */
> return dse.val;
> }
> @@ -887,7 +903,7 @@ static void __intel_pmu_pebs_event(struct perf_event *event,
> data.data_src.val = load_latency_data(pebs->dse);
> else if (event->hw.flags & PERF_X86_EVENT_PEBS_ST_HSW)
> data.data_src.val =
> - precise_store_data_hsw(pebs->dse);
> + precise_store_data_hsw(event, pebs->dse);
> else
> data.data_src.val = precise_store_data(pebs->dse);
> }
next prev parent reply other threads:[~2014-05-15 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:56 [PATCH v2]: fix Haswell precise store data source encoding Stephane Eranian
2014-05-15 19:56 ` Don Zickus [this message]
2014-05-15 20:08 ` Stephane Eranian
2014-05-15 20:27 ` Don Zickus
2014-05-15 21:22 ` Andi Kleen
2014-05-19 12:55 ` [tip:perf/core] " tip-bot for Stephane Eranian
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=20140515195655.GG50500@redhat.com \
--to=dzickus@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=ak@linux.intel.com \
--cc=eranian@google.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