[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yj8ditXSBemA41Z3@kernel.org>
Date: Sat, 26 Mar 2022 11:04:58 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Leo Yan <leo.yan@...aro.org>
Cc: Ali Saidi <alisaidi@...zon.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, german.gomez@....com,
benh@...nel.crashing.org, Nick.Forrington@....com,
alexander.shishkin@...ux.intel.com, andrew.kilroy@....com,
james.clark@....com, john.garry@...wei.com, jolsa@...nel.org,
kjain@...ux.ibm.com, lihuafei1@...wei.com, mark.rutland@....com,
mathieu.poirier@...aro.org, mingo@...hat.com, namhyung@...nel.org,
peterz@...radead.org, will@...nel.org
Subject: Re: [PATCH v4 2/4] perf arm-spe: Use SPE data source for neoverse
cores
Em Sat, Mar 26, 2022 at 09:56:53PM +0800, Leo Yan escreveu:
> On Sat, Mar 26, 2022 at 10:52:01AM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Mar 26, 2022 at 09:47:54PM +0800, Leo Yan escreveu:
> > > On Thu, Mar 24, 2022 at 06:33:21PM +0000, Ali Saidi wrote:
> > > > +static void arm_spe__synth_data_source_neoverse(const struct arm_spe_record *record,
> > > > + union perf_mem_data_src *data_src)
> > > > {
> > > > - union perf_mem_data_src data_src = { 0 };
> > > > + /*
> > > > + * Even though four levels of cache hierarchy are possible, no known
> > > > + * production Neoverse systems currently include more than three levels
> > > > + * so for the time being we assume three exist. If a production system
> > > > + * is built with four the this function would have to be changed to
> > > > + * detect the number of levels for reporting.
> > > > + */
> > > > - if (record->op == ARM_SPE_LD)
> > > > - data_src.mem_op = PERF_MEM_OP_LOAD;
> > > > - else
> > > > - data_src.mem_op = PERF_MEM_OP_STORE;
> > > Firstly, apologize that I didn't give clear idea when Ali sent patch sets
> > > v2 and v3.
> > Ok, removing this as well.
> > Thanks for reviewing.
> Thanks a lot, Arnaldo. Yeah, it's good to give a bit more time to
> dismiss the concerns in this patch.
Sure, at least it was build tested on many distros/cross compilers and
this part is ok 8-)
> Sorry again for the inconvenience.
np.
- Arnaldo
Powered by blists - more mailing lists