From: Davidlohr Bueso <dave@stgolabs.net>
To: Richard Cheng <icheng@nvidia.com>
Cc: jic23@kernel.org, will@kernel.org, mark.rutland@arm.com,
harshal.t@samsung.com, linux-cxl@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v3 3/3] perf/cxlpmu: Support Channel/Rank/Bank filter
Date: Wed, 15 Jul 2026 09:53:09 -0700 [thread overview]
Message-ID: <20260715165309.qvduacwyliu4pyoa@offworld> (raw)
In-Reply-To: <alXWrWdv-5xxHh4P@MWDK4CY14F>
On Tue, 14 Jul 2026, Richard Cheng wrote:
>On Sun, Jul 12, 2026 at 11:11:12PM +0800, Davidlohr Bueso wrote:
>> @@ -621,6 +646,32 @@ static int cxl_pmu_event_init(struct perf_event *event)
>> return -EOPNOTSUPP;
>> /* TODO: Validation of any filter */
>>
>> + if (cxl_pmu_config1_crb_filter_en(event)) {
>> + if (!info->filter_crb)
>> + return -EINVAL;
>> + /*
>> + * CRB filtering (Filter ID 1) is only valid for the DDR
>> + * Interface, Queue Occupancy, Queue Residency and Retry
>> + * event groups (CXL 4.0 Table 13-5).
>> + */
>> + switch (cxl_pmu_config_get_gid(event)) {
>> + case CXL_PMU_GID_DDR:
>> + case CXL_PMU_GID_QUEUE_OCC:
>
>Should we also validate the Event Vendor ID?
>
>GID namespace is scoped by the Vendor ID, while the groups listed
>in CXL 4.0 Table 13-5 are under CXL vendor ID.
>A vendor-specific event could reuse one of these numeric GID and pass
>this switch even though the CXL CRB rules don't apply to it.
>
>I would suggest to reject non-CXL events before the switch
>"""
>if (cxl_pmu_config_get_vid(event) != PCI_VENDOR_ID_CXL)
> return -EINVAL;
>"""
>
>Do you think this make sense to you?
Good catch, yes this makes sense.
Thanks,
Davidlohr
prev parent reply other threads:[~2026-07-15 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 6:11 [PATCH v3 0/3] perf/cxlpmu: Misc updates Davidlohr Bueso
2026-07-13 6:11 ` [PATCH v3 1/3] perf/cxlpmu: Fix 64-bit write to 32-bit HDM filter register Davidlohr Bueso
2026-07-14 6:40 ` Richard Cheng
2026-07-13 6:11 ` [PATCH v3 2/3] perf/cxlpmu: Add missing CXL 4.0 events Davidlohr Bueso
2026-07-13 6:11 ` [PATCH v3 3/3] perf/cxlpmu: Support Channel/Rank/Bank filter Davidlohr Bueso
2026-07-14 6:35 ` Richard Cheng
2026-07-15 16:53 ` Davidlohr Bueso [this message]
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=20260715165309.qvduacwyliu4pyoa@offworld \
--to=dave@stgolabs.net \
--cc=harshal.t@samsung.com \
--cc=icheng@nvidia.com \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/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