From: German Gomez <german.gomez@arm.com> To: Leo Yan <leo.yan@linaro.org>, Ali Saidi <alisaidi@amazon.com> Cc: acme@kernel.org, alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com, benh@kernel.crashing.org, james.clark@arm.com, john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com, lihuafei1@huawei.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, mark.rutland@arm.com, mathieu.poirier@linaro.org, mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org, will@kernel.org, yao.jin@linux.intel.com, Nick.Forrington@arm.com Subject: Re: [PATCH v2 2/2] perf mem: Support HITM for when mem_lvl_num is used Date: Wed, 16 Mar 2022 15:10:55 +0000 [thread overview] Message-ID: <1637567b-42df-57d5-2987-939ffbf451ef@arm.com> (raw) In-Reply-To: <20220316124208.GA310478@leoy-ThinkPad-X240s> On 16/03/2022 12:42, Leo Yan wrote: > On Wed, Mar 16, 2022 at 11:43:52AM +0000, German Gomez wrote: > > [...] > >>>>> I had a look at the TRMs for the N1[1], V1[2] and N2[3] Neoverse cores >>>>> (specifically the LL_CACHE_RD pmu events). If we were to assign a number >>>>> to the system cache (assuming all caches are implemented): >>>>> >>>>> *For N1*, if L2 and L3 are implemented, system cache would follow at *L4* >>>> To date no one has built 4 level though. Everyone has only built three. >>> The N1SDP board advertises 4 levels (we use it regularly for testing perf patches) >> That said, it's probably the odd one out. >> >> I'm not against assuming 3 levels. Later if there's is a strong need for L4, indeed we can go back and change it. > Thanks for the info. > > For exploring cache hierarchy via sysFS is a good idea, the only one > concern for me is: can we simply take the system cache as the same > thing as the highest level cache? If so, I think another option is to For Neoverse, it should be. LL_CACHE_RD pmu event says (if system cache is implemented): * If CPUECTLR.EXTLLC is set: This event counts any cacheable read transaction which returns a data source of 'interconnect cache'. > define a cache level as "PERF_MEM_LVLNUM_SYSTEM_CACHE" and extend the > decoding code for support it. > > With PERF_MEM_LVLNUM_SYSTEM_CACHE, it can tell users clearly the data > source from system cache, and users can easily map this info with the > cache media on the working platform. > > In practice, I don't object to use cache level 3 at first step. At > least this can meet the requirement at current stage. Ok, I agree. I think for now it is a good compromise. Detecting the caches seems like an additional/separate perf feature. Thanks, German > Thanks, > Leo
WARNING: multiple messages have this Message-ID (diff)
From: German Gomez <german.gomez@arm.com> To: Leo Yan <leo.yan@linaro.org>, Ali Saidi <alisaidi@amazon.com> Cc: acme@kernel.org, alexander.shishkin@linux.intel.com, andrew.kilroy@arm.com, benh@kernel.crashing.org, james.clark@arm.com, john.garry@huawei.com, jolsa@kernel.org, kjain@linux.ibm.com, lihuafei1@huawei.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, mark.rutland@arm.com, mathieu.poirier@linaro.org, mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org, will@kernel.org, yao.jin@linux.intel.com, Nick.Forrington@arm.com Subject: Re: [PATCH v2 2/2] perf mem: Support HITM for when mem_lvl_num is used Date: Wed, 16 Mar 2022 15:10:55 +0000 [thread overview] Message-ID: <1637567b-42df-57d5-2987-939ffbf451ef@arm.com> (raw) In-Reply-To: <20220316124208.GA310478@leoy-ThinkPad-X240s> On 16/03/2022 12:42, Leo Yan wrote: > On Wed, Mar 16, 2022 at 11:43:52AM +0000, German Gomez wrote: > > [...] > >>>>> I had a look at the TRMs for the N1[1], V1[2] and N2[3] Neoverse cores >>>>> (specifically the LL_CACHE_RD pmu events). If we were to assign a number >>>>> to the system cache (assuming all caches are implemented): >>>>> >>>>> *For N1*, if L2 and L3 are implemented, system cache would follow at *L4* >>>> To date no one has built 4 level though. Everyone has only built three. >>> The N1SDP board advertises 4 levels (we use it regularly for testing perf patches) >> That said, it's probably the odd one out. >> >> I'm not against assuming 3 levels. Later if there's is a strong need for L4, indeed we can go back and change it. > Thanks for the info. > > For exploring cache hierarchy via sysFS is a good idea, the only one > concern for me is: can we simply take the system cache as the same > thing as the highest level cache? If so, I think another option is to For Neoverse, it should be. LL_CACHE_RD pmu event says (if system cache is implemented): * If CPUECTLR.EXTLLC is set: This event counts any cacheable read transaction which returns a data source of 'interconnect cache'. > define a cache level as "PERF_MEM_LVLNUM_SYSTEM_CACHE" and extend the > decoding code for support it. > > With PERF_MEM_LVLNUM_SYSTEM_CACHE, it can tell users clearly the data > source from system cache, and users can easily map this info with the > cache media on the working platform. > > In practice, I don't object to use cache level 3 at first step. At > least this can meet the requirement at current stage. Ok, I agree. I think for now it is a good compromise. Detecting the caches seems like an additional/separate perf feature. Thanks, German > Thanks, > Leo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-16 15:13 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-21 22:47 [PATCH v2 1/2] perf arm-spe: Use SPE data source for neoverse cores Ali Saidi 2022-02-21 22:47 ` Ali Saidi 2022-02-21 22:48 ` [PATCH v2 2/2] perf mem: Support HITM for when mem_lvl_num is used Ali Saidi 2022-02-21 22:48 ` Ali Saidi 2022-03-02 15:39 ` German Gomez 2022-03-02 15:39 ` German Gomez 2022-03-13 12:44 ` Leo Yan 2022-03-13 12:44 ` Leo Yan 2022-03-13 19:19 ` Ali Saidi 2022-03-13 19:19 ` Ali Saidi 2022-03-14 6:33 ` Leo Yan 2022-03-14 6:33 ` Leo Yan 2022-03-14 18:00 ` German Gomez 2022-03-14 18:00 ` German Gomez 2022-03-14 18:37 ` Ali Saidi 2022-03-14 18:37 ` Ali Saidi 2022-03-15 18:44 ` German Gomez 2022-03-15 18:44 ` German Gomez 2022-03-16 11:43 ` German Gomez 2022-03-16 11:43 ` German Gomez 2022-03-16 12:42 ` Leo Yan 2022-03-16 12:42 ` Leo Yan 2022-03-16 15:10 ` German Gomez [this message] 2022-03-16 15:10 ` German Gomez 2022-03-02 11:59 ` [PATCH v2 1/2] perf arm-spe: Use SPE data source for neoverse cores German Gomez 2022-03-02 11:59 ` German Gomez 2022-03-13 11:46 ` Leo Yan 2022-03-13 11:46 ` Leo Yan 2022-03-13 19:06 ` Ali Saidi 2022-03-13 19:06 ` Ali Saidi 2022-03-14 4:05 ` Leo Yan 2022-03-14 4:05 ` Leo Yan
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=1637567b-42df-57d5-2987-939ffbf451ef@arm.com \ --to=german.gomez@arm.com \ --cc=Nick.Forrington@arm.com \ --cc=acme@kernel.org \ --cc=alexander.shishkin@linux.intel.com \ --cc=alisaidi@amazon.com \ --cc=andrew.kilroy@arm.com \ --cc=benh@kernel.crashing.org \ --cc=james.clark@arm.com \ --cc=john.garry@huawei.com \ --cc=jolsa@kernel.org \ --cc=kjain@linux.ibm.com \ --cc=leo.yan@linaro.org \ --cc=lihuafei1@huawei.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-perf-users@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=mathieu.poirier@linaro.org \ --cc=mingo@redhat.com \ --cc=namhyung@kernel.org \ --cc=peterz@infradead.org \ --cc=will@kernel.org \ --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.