From: Andi Kleen <ak@linux.intel.com>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH] perf script: add script to profile and resolve physical mem type
Date: Tue, 17 Oct 2017 14:28:12 -0700 [thread overview]
Message-ID: <20171017212812.GT5109@tassilo.jf.intel.com> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F077537D6C9F@SHSMSX103.ccr.corp.intel.com>
On Tue, Oct 17, 2017 at 09:10:16PM +0000, Liang, Kan wrote:
> > >
> > > Right, it doesn’t need load latency. 0x81d0 should be a better choice.
> > > I will use 0x81d0 and 0x82d0 as default event for V2.
> >
> > That's model specific. You would need to check the model number if you do
> > that.
> >
> > Also with modern perf you can use the correct event names of course.
>
> The event names are model specific as well.
> For Mem load events,
> MEM_INST_RETIRED.ALL_LOADS is the event name for skylake.
> MEM_UOPS_RETIRED.ALL_LOADS is the event name for the rest of platforms.
> I think it still need to check the model number.
You can just try the common variations, or grep them in perf list output.
-Andi
prev parent reply other threads:[~2017-10-17 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 22:26 kan.liang
2017-10-17 19:22 ` Stephane Eranian
2017-10-17 19:54 ` Liang, Kan
2017-10-17 19:58 ` Stephane Eranian
2017-10-17 20:24 ` Liang, Kan
2017-10-17 20:49 ` Andi Kleen
2017-10-17 21:10 ` Liang, Kan
2017-10-17 21:28 ` 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=20171017212812.GT5109@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®