[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8fb8d32d-cdda-b0c9-d863-a5e63ab56285@amd.com>
Date: Fri, 14 Oct 2022 20:34:58 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
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>,
Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH v3 01/15] perf/mem: Introduce
PERF_MEM_LVLNUM_{EXTN_MEM|IO}
> Its already upstream, so please go on from there, ok?
Right. Only PERF_MEM_LVLNUM_EXTN_MEM -> PERF_MEM_LVLNUM_CXL kernel side
patch is pending. Tool side already uses PERF_MEM_LVLNUM_CXL macro.
Peter, let me know if you want me to resend.
Thanks,
Ravi
Powered by blists - more mailing lists