[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00865c8f-32eb-157f-ce05-2d5d0218559e@amd.com>
Date: Fri, 30 Jun 2023 12:05:28 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: peterz@...radead.org
Cc: mingo@...nel.org, eranian@...gle.com, kan.liang@...ux.intel.com,
jolsa@...nel.org, irogers@...gle.com, adrian.hunter@...el.com,
leo.yan@...aro.org, kjain@...ux.ibm.com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
sandipan.das@....com, ananth.narayan@....com,
santosh.shukla@....com, Namhyung Kim <namhyung@...nel.org>,
acme@...nel.org, Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH v3 0/9] perf/mem: AMD IBS and generic tools improvements
On 29-May-23 9:35 AM, Ravi Bangoria wrote:
> On 16-May-23 8:15 AM, Ravi Bangoria wrote:
>> On 10-Apr-23 7:53 AM, Ravi Bangoria wrote:
>>> On 08-Apr-23 3:14 AM, Namhyung Kim wrote:
>>>> Hi Ravi,
>>>>
>>>> On Fri, Apr 7, 2023 at 4:25 AM Ravi Bangoria <ravi.bangoria@....com> wrote:
>>>>>
>>>>> Kernel IBS driver wasn't using new PERF_MEM_* APIs due to some of its
>>>>> limitations. Mainly:
>>>>>
>>>>> 1. mem_lvl_num doesn't allow setting multiple sources whereas old API
>>>>> allows it. Setting multiple data sources is useful because IBS on
>>>>> pre-zen4 uarch doesn't provide fine granular DataSrc details (there
>>>>> is only one such DataSrc(2h) though).
>>>>> 2. perf mem sorting logic (sort__lvl_cmp()) ignores mem_lvl_num. perf
>>>>> c2c (c2c_decode_stats()) does not use mem_lvl_num at all. perf mem
>>>>> prints mem_lvl and mem_lvl_num both if both are set, which is ugly.
>>>>>
>>>>> Set mem_lvl_num, mem_remote and mem_hops for data_src via IBS. Handle
>>>>> first issue using mem_lvl_num = ANY_CACHE | HOPS_0. In addition to
>>>>> setting new API fields, convert all individual field assignments to
>>>>> compile time wrapper macros built using PERF_MEM_S(). Also convert
>>>>> DataSrc conditional code to array lookups.
>>>>>
>>>>> Interpretation of perf_mem_data_src by perf_mem__lvl_scnprintf() was
>>>>> non-intuitive. Make it sane.
>>>>
>>>> Looks good, but I think you need to split kernel and user patches.
>>>
>>> Patch #1 to #3 are kernel changes. Patch #4 to #9 are userspace changes.
>>> Arnaldo, Peter, please let me know if you wants to split the series and
>>> resend.
>>
>> Hi Peter, tools/ patches are already upstream. Can you please pick up
>> kernel changes.
>
> Gentle ping, Peter!
Hello Peter, this is pending from long time. Can you please consider taking
it. Please let me know if you want me to resend the patches.
Thanks,
Ravi
Powered by blists - more mailing lists