[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e09af67-a416-4ead-b406-6c8b998de344@linux.intel.com>
Date: Sat, 23 Apr 2022 05:53:28 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Leo Yan <leo.yan@...aro.org>, Ali Saidi <alisaidi@...zon.com>
Cc: kan.liang@...ux.intel.com, Nick.Forrington@....com,
acme@...nel.org, alexander.shishkin@...ux.intel.com,
andrew.kilroy@....com, benh@...nel.crashing.org,
german.gomez@....com, james.clark@....com, john.garry@...wei.com,
jolsa@...nel.org, kjain@...ux.ibm.com, lihuafei1@...wei.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org, mark.rutland@....com,
mathieu.poirier@...aro.org, mingo@...hat.com, namhyung@...nel.org,
peterz@...radead.org, will@...nel.org
Subject: Re: [PATCH v5 2/5] perf: Add SNOOP_PEER flag to perf mem data struct
> Except SNOOPX_FWD means a no modified cache snooping, it also means it's
> a cache conherency from *remote* socket. This is quite different from we
> define SNOOPX_PEER, which only snoop from peer CPU or clusters.
>
> If no objection, I prefer we could keep the new snoop type SNOOPX_PEER,
> this would be easier for us to distinguish the semantics and support the
> statistics for SNOOPX_FWD and SNOOPX_PEER separately.
>
> I overlooked the flag SNOOPX_FWD, thanks a lot for Kan's reminding.
Yes seems better to keep using a separate flag if they don't exactly match.
It's not that we're short on flags anyways.
-Andi
Powered by blists - more mailing lists