From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 2/4] perf/x86: Fix data source decoding for Skylake
Date: Thu, 8 Jun 2017 13:10:07 -0700 [thread overview]
Message-ID: <20170608201007.GH8096@two.firstfloor.org> (raw)
In-Reply-To: <CABPqkBRqyu0m42ErD8ut5=tyPRjOZzEKxrdWo0aAq1J7xAQFsg@mail.gmail.com>
On Thu, Jun 08, 2017 at 12:40:59PM -0700, Stephane Eranian wrote:
> Hi,
>
> On Thu, Jun 8, 2017 at 1:15 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Wed, Jun 07, 2017 at 04:22:24PM -0700, Andi Kleen wrote:
> >
> > > diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
> > > index b1c0b187acfe..95daade294d7 100644
> > > --- a/include/uapi/linux/perf_event.h
> > > +++ b/include/uapi/linux/perf_event.h
> > > @@ -931,14 +931,18 @@ union perf_mem_data_src {
> > > mem_snoop:5, /* snoop mode */
> > > mem_lock:2, /* lock instr */
> > > mem_dtlb:7, /* tlb access */
> > > - mem_rsvd:31;
> > > + mem_lvlx:8, /* memory hierarchy level, ext */
> > > + mem_snoopx:2, /* snoop mode, ext */
> > > + mem_rsvd:21;
> > > };
> > > };
> > > #elif defined(__BIG_ENDIAN_BITFIELD)
> > > union perf_mem_data_src {
> > > __u64 val;
> > > struct {
> > > - __u64 mem_rsvd:31,
> > > + __u64 mem_rsvd:21,
> > > + mem_snoopx:2, /* snoop mode, ext */
> > > + mem_lvlx:8, /* memory hierarchy level, ext */
> > > mem_dtlb:7, /* tlb access */
> > > mem_lock:2, /* lock instr */
> > > mem_snoop:5, /* snoop mode */
> >
> > So one thing we could do is add a mem_hops field and always set that,
> > even for the old stuff. The old stuff will not know about that field and
> > ignore the bits, but new stuff will then not need as many LVL bits.
Note that Skylake cannot fill it in, it doesn't report the hops.
And for the old parts the existing bits work. So I don't think
there's a motivation to add a new hops field, unless some other
architecture needs it.
> >
> That would be better than lvlx I think. I am guessing you're suggesting
> an integer count here and not a bitmask. Right? Then I wonder why it
> would need 8 bits or 255 possible levels!
Sure counts are better than bits. At least it's a far more efficient
encoding. Ok so add a new level_num field, and use one count for
PMEM and L4, and also fill in for the others.
> > > +#define PERF_MEM_LVLX_PMEM 0x08 /* Persistent Memory */
> > > +#define PERF_MEM_LVLX_REM_PMEM 0x10 /* Remote Persistent Memory */
> > > +#define PERF_MEM_LVLX_REM_NA 0x20 /* Remote N/A level */
> >
> > Still wondering what the point of REM_NA is.. can you explain?
It's a remote cache, but the hardware doesn't report which one,
and also doesn't report the hops.
Ok PERF_MEM_LVL_REM_CCE would be a better name I guess, fitting
with the existing ones.
-Andi
next prev parent reply other threads:[~2017-06-08 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 23:22 Fix Skylake PEBS data source for perf Andi Kleen
2017-06-07 23:22 ` [PATCH v2 1/4] perf/x86: Move Nehalem PEBS code to flag Andi Kleen
2017-06-07 23:22 ` [PATCH v2 2/4] perf/x86: Fix data source decoding for Skylake Andi Kleen
2017-06-08 8:15 ` Peter Zijlstra
2017-06-08 19:40 ` Stephane Eranian
2017-06-08 20:03 ` Peter Zijlstra
2017-06-09 16:47 ` Andi Kleen
2017-06-08 20:10 ` Andi Kleen [this message]
2017-06-08 20:22 ` Peter Zijlstra
2017-06-09 8:04 ` Madhavan Srinivasan
2017-06-07 23:22 ` [PATCH v2 3/4] perf, tools: Add support for printing new mem_info encodings Andi Kleen
2017-06-07 23:22 ` [PATCH v2 4/4] perf, tools: Add test cases for new data source encoding 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=20170608201007.GH8096@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sukadev@linux.vnet.ibm.com \
/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).