From: Kajol Jain <kjain@linux.ibm.com> To: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org, ak@linux.intel.com Cc: 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, kjain@linux.ibm.com Subject: [PATCH v3 0/4] Add mem_hops field in perf_mem_data_src structure Date: Wed, 6 Oct 2021 19:36:50 +0530 [thread overview] Message-ID: <20211006140654.298352-1-kjain@linux.ibm.com> (raw) Patch set adds a new field called 'mem_hops' in the perf_mem_data_src structure which can be used to represent intra-node/package or inter-node/off-package details. This field is of size 3 bits where PERF_MEM_HOPS_{NA, 0..6} value can be used to present different hop levels data. Patch 1 of the patch-set adds a comment about current state of PERF_MEM_LVL_* namespace and remove an extra line present in perf_mem__lvl_scnprintf function. Patch 2 & 3 adds tool and kernel side changes to add mem_hops field. Patch 4 of the patch-set fix the data source encodings to represent L2.1/L3.1 cache access data for powerpc platform. Changelog: v2 -> v3 - Since added field HOPS related to NUMA, update the data presented by HOPS_0 to denotes accesses from 'remote core, same node' as suggested by Peter Zijlstra. - Link to the patchset v2: https://lkml.org/lkml/2021/10/5/271 v1 -> v2: - Rather then adding new macros for L2.1/L3.1 (same chip, different core) entries as part of field lvlnum, we are introducing new field called 'mem_hops' which can be used to get hops level data(intra-chip/package or inter-chip/off-package details). As suggested by Peter Zijlstra. - Using OnChip to denote data accesses from 'another core of same chip' is not too clear. Update it to 'remote core, same chip' as pointed by Michael Ellerman. - Update the fix patch of correcting data source encodings to use new added field 'mem_hops' - Link to the patchset v1: https://lkml.org/lkml/2021/9/4/37 Kajol Jain (4): perf: Add comment about current state of PERF_MEM_LVL_* namespace and remove an extra line perf: Add mem_hops field in perf_mem_data_src structure tools/perf: Add mem_hops field in perf_mem_data_src structure powerpc/perf: Fix data source encodings for L2.1 and L3.1 accesses arch/powerpc/perf/isa207-common.c | 26 +++++++++++++++++++++----- arch/powerpc/perf/isa207-common.h | 2 ++ include/uapi/linux/perf_event.h | 19 ++++++++++++++++--- tools/include/uapi/linux/perf_event.h | 19 ++++++++++++++++--- tools/perf/util/mem-events.c | 20 ++++++++++++++++++-- 5 files changed, 73 insertions(+), 13 deletions(-) -- 2.26.2
WARNING: multiple messages have this Message-ID (diff)
From: Kajol Jain <kjain@linux.ibm.com> To: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, jolsa@kernel.org, namhyung@kernel.org, ak@linux.intel.com Cc: mark.rutland@arm.com, songliubraving@fb.com, atrajeev@linux.vnet.ibm.com, daniel@iogearbox.net, rnsastry@linux.ibm.com, alexander.shishkin@linux.intel.com, kjain@linux.ibm.com, ast@kernel.org, linux-perf-users@vger.kernel.org, yao.jin@linux.intel.com, maddy@linux.ibm.com, paulus@samba.org, kan.liang@linux.intel.com Subject: [PATCH v3 0/4] Add mem_hops field in perf_mem_data_src structure Date: Wed, 6 Oct 2021 19:36:50 +0530 [thread overview] Message-ID: <20211006140654.298352-1-kjain@linux.ibm.com> (raw) Patch set adds a new field called 'mem_hops' in the perf_mem_data_src structure which can be used to represent intra-node/package or inter-node/off-package details. This field is of size 3 bits where PERF_MEM_HOPS_{NA, 0..6} value can be used to present different hop levels data. Patch 1 of the patch-set adds a comment about current state of PERF_MEM_LVL_* namespace and remove an extra line present in perf_mem__lvl_scnprintf function. Patch 2 & 3 adds tool and kernel side changes to add mem_hops field. Patch 4 of the patch-set fix the data source encodings to represent L2.1/L3.1 cache access data for powerpc platform. Changelog: v2 -> v3 - Since added field HOPS related to NUMA, update the data presented by HOPS_0 to denotes accesses from 'remote core, same node' as suggested by Peter Zijlstra. - Link to the patchset v2: https://lkml.org/lkml/2021/10/5/271 v1 -> v2: - Rather then adding new macros for L2.1/L3.1 (same chip, different core) entries as part of field lvlnum, we are introducing new field called 'mem_hops' which can be used to get hops level data(intra-chip/package or inter-chip/off-package details). As suggested by Peter Zijlstra. - Using OnChip to denote data accesses from 'another core of same chip' is not too clear. Update it to 'remote core, same chip' as pointed by Michael Ellerman. - Update the fix patch of correcting data source encodings to use new added field 'mem_hops' - Link to the patchset v1: https://lkml.org/lkml/2021/9/4/37 Kajol Jain (4): perf: Add comment about current state of PERF_MEM_LVL_* namespace and remove an extra line perf: Add mem_hops field in perf_mem_data_src structure tools/perf: Add mem_hops field in perf_mem_data_src structure powerpc/perf: Fix data source encodings for L2.1 and L3.1 accesses arch/powerpc/perf/isa207-common.c | 26 +++++++++++++++++++++----- arch/powerpc/perf/isa207-common.h | 2 ++ include/uapi/linux/perf_event.h | 19 ++++++++++++++++--- tools/include/uapi/linux/perf_event.h | 19 ++++++++++++++++--- tools/perf/util/mem-events.c | 20 ++++++++++++++++++-- 5 files changed, 73 insertions(+), 13 deletions(-) -- 2.26.2
next reply other threads:[~2021-10-06 14:08 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-06 14:06 Kajol Jain [this message] 2021-10-06 14:06 ` [PATCH v3 0/4] Add mem_hops field in perf_mem_data_src structure Kajol Jain 2021-10-06 14:06 ` [PATCH v3 1/4] perf: Add comment about current state of PERF_MEM_LVL_* namespace and remove an extra line Kajol Jain 2021-10-06 14:06 ` Kajol Jain 2021-10-19 15:35 ` [tip: perf/core] " tip-bot2 for Kajol Jain 2021-10-06 14:06 ` [PATCH v3 2/4] perf: Add mem_hops field in perf_mem_data_src structure Kajol Jain 2021-10-06 14:06 ` Kajol Jain 2021-10-19 15:35 ` [tip: perf/core] " tip-bot2 for Kajol Jain 2021-10-06 14:06 ` [PATCH v3 3/4] tools/perf: " Kajol Jain 2021-10-06 14:06 ` Kajol Jain 2021-10-19 15:35 ` [tip: perf/core] " tip-bot2 for Kajol Jain 2021-10-06 14:06 ` [PATCH v3 4/4] powerpc/perf: Fix data source encodings for L2.1 and L3.1 accesses Kajol Jain 2021-10-06 14:06 ` Kajol Jain 2021-10-19 15:35 ` [tip: perf/core] " tip-bot2 for Kajol Jain 2021-10-07 6:49 ` [PATCH v3 0/4] Add mem_hops field in perf_mem_data_src structure Peter Zijlstra 2021-10-07 6:49 ` Peter Zijlstra 2021-10-18 3:46 ` Michael Ellerman 2021-10-18 3:46 ` Michael Ellerman 2021-10-18 9:48 ` Peter Zijlstra 2021-10-18 9:48 ` Peter Zijlstra
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=20211006140654.298352-1-kjain@linux.ibm.com \ --to=kjain@linux.ibm.com \ --cc=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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.