From: Peter Zijlstra <peterz@infradead.org>
To: James Clark <james.clark@linaro.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Leo Yan <leo.yan@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-doc@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH v9 2/5] perf: arm_spe: Add support for filtering on data source
Date: Tue, 11 Nov 2025 11:55:26 +0100 [thread overview]
Message-ID: <20251111105526.GI278048@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <8078e440-e97c-425c-b046-987b642640f7@linaro.org>
On Tue, Nov 11, 2025 at 10:51:56AM +0000, James Clark wrote:
>
>
> On 10/11/2025 3:48 pm, Peter Zijlstra wrote:
> > On Wed, Oct 29, 2025 at 03:46:02PM +0000, James Clark wrote:
> > > SPE_FEAT_FDS adds the ability to filter on the data source of packets.
> > > Like the other existing filters, enable filtering with PMSFCR_EL1.FDS
> > > when any of the filter bits are set.
> > >
> > > Each bit maps to data sources 0-63 described by bits[0:5] in the data
> > > source packet (although the full range of data source is 16 bits so
> > > higher value data sources can't be filtered on). The filter is an OR of
> > > all the bits, so for example clearing bits 0 and 3 only includes packets
> > > from data sources 0 OR 3.
> > >
> > > Invert the filter given by userspace so that the default value of 0 is
> > > equivalent to including all values (no filtering). This allows us to
> > > skip adding a new format bit to enable filtering and still support
> > > excluding all data sources which would have been a filter value of 0 if
> > > not for the inversion.
> >
> > So from that I'm reading the config4 field will only have like 16 bits,
>
> The _data source_ is 16 bits, but the _data source filter_ is 64 bits.
Ah!
> It might be clearer if I add a few more words to differentiate "data source"
> and "filter":
>
> Each bit of the 64 bit filter maps to data sources 0-63 described by
> bits[0:5] in the data source packet (although the full range of data
> source is 16 bits so higher value data sources can't be filtered on).
> The filter is an OR of all the filter bits, so for example clearing
> filter bits 0 and 3 only includes packets from data sources 0 OR 3.
Yeah, that might've helped :-)
next prev parent reply other threads:[~2025-11-11 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 15:46 [PATCH v9 0/5] perf: arm_spe: Armv8.8 SPE features James Clark
2025-10-29 15:46 ` [PATCH v9 1/5] perf: Add perf_event_attr::config4 James Clark
2025-11-03 14:33 ` Will Deacon
2025-11-11 10:55 ` Peter Zijlstra
2025-10-29 15:46 ` [PATCH v9 2/5] perf: arm_spe: Add support for filtering on data source James Clark
2025-11-10 15:48 ` Peter Zijlstra
2025-11-11 10:51 ` James Clark
2025-11-11 10:55 ` Peter Zijlstra [this message]
2025-10-29 15:46 ` [PATCH v9 3/5] tools headers UAPI: Sync linux/perf_event.h with the kernel sources James Clark
2025-10-29 15:46 ` [PATCH v9 4/5] perf tools: Add support for perf_event_attr::config4 James Clark
2025-10-29 15:46 ` [PATCH v9 5/5] perf docs: arm-spe: Document new SPE filtering features James Clark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251111105526.GI278048@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=joey.gouly@arm.com \
--cc=jolsa@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®