From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@elte.hu
Subject: Re: [PATCH] perf/x86: fix load latency/precise store data source issues
Date: Tue, 5 Aug 2014 14:37:34 -0700 [thread overview]
Message-ID: <20140805213734.GI5803@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140805041333.GA17598@quad>
On Tue, Aug 05, 2014 at 06:13:33AM +0200, Stephane Eranian wrote:
>
> This patch fixes some issues introduced by Andi's 'Revamp
> PEBS' event selection patch (which is under review right now).
>
> Most of the issues were related to the encoding of the
> data source, for PEBS events in general and load/store
> events on Haswell.
>
> This patchd does:
> - the default of 0 in perf_sample_data_init() was wrong. 0 is not
> a valid value. So defined PERF_MEM_NA (not available)
Looks good.
>
> - On HSW, renamed your precise_store_hsw() to datala_hsw()
> because you are actually processing both loads and stores, except
> the load latency event which goes thru normal function
Pleae don't mix cleanups with bug fixes.
>
> - precise_store_data_hsw() was returning bogus data source for store
> events. dse.mem_lvl instead of dse.val
This was already fixed in the second patch (and it wasn't introduced
by my patch):
commit 57f6c0e81f5b82b341c4c4ddd621531788c50433
Author: Andi Kleen <ak@linux.intel.com>
Date: Fri Jul 18 17:41:48 2014 -0700
perf, x86: Fix haswell mem hierarchy flags reporting
This fixes a bug introduced with
commit 722e76e60f2775c21b087ff12c5e678cf0ebcaaf
Author: Stephane Eranian <eranian@google.com>
Date: Thu May 15 17:56:44 2014 +0200
fix Haswell precise store data source encoding
When returning early we need to return the complete value of the
memory hierarchy, not just the mem_lvl. Otherwise any load/store/na
flags set early get lost.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
-Andi
prev parent reply other threads:[~2014-08-05 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 4:13 Stephane Eranian
2014-08-05 21:37 ` Andi Kleen [this message]
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=20140805213734.GI5803@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=eranian@google.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
Powered by JetHome