From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Kajol Jain <kjain@linux.ibm.com>
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, jolsa@kernel.org, namhyung@kernel.org,
ak@linux.intel.com, linux-perf-users@vger.kernel.org,
maddy@linux.ibm.com, atrajeev@linux.vnet.ibm.com,
rnsastry@linux.ibm.com, yao.jin@linux.intel.com, ast@kernel.org,
daniel@iogearbox.net, songliubraving@fb.com,
kan.liang@linux.intel.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, paulus@samba.org
Subject: Re: [PATCH 0/4] perf: Add new macros for mem_hops field
Date: Thu, 9 Dec 2021 16:17:41 -0300 [thread overview]
Message-ID: <YbJWVYZg1el9PR1I@kernel.org> (raw)
In-Reply-To: <20211206091749.87585-1-kjain@linux.ibm.com>
Em Mon, Dec 06, 2021 at 02:47:45PM +0530, Kajol Jain escreveu:
> Patchset adds new macros for mem_hops field which can be
> used to represent remote-node, socket and board level details.
>
> Currently the code had macro for HOPS_0, which corresponds
> to data coming from another core but same node.
> Add new macros for HOPS_1 to HOPS_3 to represent
> remote-node, socket and board level data.
>
> For ex: Encodings for mem_hops fields with L2 cache:
I checked and this hasn't hit mainstream, is it already merged on a tree
where this is slated to be submitted in the next window? If so please
let me know which one so that I can merge it on perf/core.
- Arnaldo
> L2 - local L2
> L2 | REMOTE | HOPS_0 - remote core, same node L2
> L2 | REMOTE | HOPS_1 - remote node, same socket L2
> L2 | REMOTE | HOPS_2 - remote socket, same board L2
> L2 | REMOTE | HOPS_3 - remote board L2
>
> Patch 1 & 2 adds tool and kernel side changes to add new macros for
> mem_hops field
>
> Patch 3 add data source encodings for power10 and older platforms
> to represent data based on newer composite PERF_MEM_LVLNUM* fields
>
> Patch 4 add data source encodings with proper sub_index used to
> represent memory/cache level data for power10 platform.
>
> Kajol Jain (4):
> perf: Add new macros for mem_hops field
> tools/perf: Add new macros for mem_hops field
> powerpc/perf: Add encodings to represent data based on newer composite
> PERF_MEM_LVLNUM* fields
> powerpc/perf: Add data source encodings for power10 platform
>
> arch/powerpc/perf/isa207-common.c | 60 ++++++++++++++++++++-------
> include/uapi/linux/perf_event.h | 5 ++-
> tools/include/uapi/linux/perf_event.h | 5 ++-
> tools/perf/util/mem-events.c | 29 ++++++++-----
> 4 files changed, 71 insertions(+), 28 deletions(-)
>
> --
> 2.27.0
--
- Arnaldo
next prev parent reply other threads:[~2021-12-09 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 9:17 [PATCH 0/4] perf: Add new macros for mem_hops field Kajol Jain
2021-12-06 9:17 ` [PATCH 1/4] " Kajol Jain
2021-12-10 8:21 ` Peter Zijlstra
2021-12-06 9:17 ` [PATCH 2/4] tools/perf: " Kajol Jain
2021-12-22 12:36 ` Arnaldo Carvalho de Melo
2021-12-06 9:17 ` [PATCH 3/4] powerpc/perf: Add encodings to represent data based on newer composite PERF_MEM_LVLNUM* fields Kajol Jain
2021-12-22 12:38 ` Arnaldo Carvalho de Melo
2021-12-06 9:17 ` [PATCH 4/4] powerpc/perf: Add data source encodings for power10 platform Kajol Jain
2021-12-22 12:41 ` Arnaldo Carvalho de Melo
2021-12-09 19:17 ` Arnaldo Carvalho de Melo [this message]
2021-12-10 6:35 ` [PATCH 0/4] perf: Add new macros for mem_hops field Michael Ellerman
2021-12-10 8:22 ` Peter Zijlstra
2021-12-21 12:14 ` Michael Ellerman
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=YbJWVYZg1el9PR1I@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ast@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rnsastry@linux.ibm.com \
--cc=songliubraving@fb.com \
--cc=yao.jin@linux.intel.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).