[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y0lpylA86mEnmefg@kernel.org>
Date: Fri, 14 Oct 2022 10:53:14 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ravi Bangoria <ravi.bangoria@....com>
Cc: "Liang, Kan" <kan.liang@...ux.intel.com>, peterz@...radead.org,
jolsa@...nel.org, namhyung@...nel.org, eranian@...gle.com,
irogers@...gle.com, jmario@...hat.com, leo.yan@...aro.org,
alisaidi@...zon.com, ak@...ux.intel.com,
dave.hansen@...ux.intel.com, hpa@...or.com, mingo@...hat.com,
mark.rutland@....com, alexander.shishkin@...ux.intel.com,
tglx@...utronix.de, bp@...en8.de, x86@...nel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
sandipan.das@....com, ananth.narayan@....com, kim.phillips@....com,
santosh.shukla@....com, kajoljain <kjain@...ux.ibm.com>
Subject: Re: [PATCH v3 01/15] perf/mem: Introduce
PERF_MEM_LVLNUM_{EXTN_MEM|IO}
Em Thu, Oct 06, 2022 at 05:08:55PM +0530, Ravi Bangoria escreveu:
> On 03-Oct-22 6:45 PM, Liang, Kan wrote:
> >> PERF_MEM_LVLNUM_EXTN_MEM was introduced to cover CXL devices but it's
> >> bit ambiguous name and also not generic enough to cover cxl.cache and
> >> cxl.io devices. Rename it to PERF_MEM_LVLNUM_CXL to be more specific.
> > Looks good to me.
> > Reviewed-by: Kan Liang <kan.liang@...ux.intel.com>
> Thanks Kan.
> Peter, can you please include this patch along with the series?
> Arnaldo, I'll respin tool side of patches with this change.
Its already upstream, so please go on from there, ok?
I'm now processing perf patches after getting lost in pahole land for a
bit :-)
- Arnaldo
Powered by blists - more mailing lists