Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Will Deacon <will@kernel.org>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	jic23@kernel.org, mark.rutland@arm.com, harshal.t@samsung.com,
	icheng@nvidia.com, linux-cxl@vger.kernel.org,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v4 0/3] perf/cxlpmu: Misc updates
Date: Thu, 16 Jul 2026 10:05:54 -0700	[thread overview]
Message-ID: <f7dfe837-a044-4d2e-bdb6-599157063eef@intel.com> (raw)
In-Reply-To: <alkLGe4PfVK12lbQ@willie-the-truck>



On 7/16/26 9:47 AM, Will Deacon wrote:
> On Thu, Jul 16, 2026 at 09:46:05AM -0700, Dave Jiang wrote:
>>
>>
>> On 7/15/26 12:14 PM, Davidlohr Bueso wrote:
>>> Hello,
>>>
>>> Changes from v3 (https://lore.kernel.org/all/20260713061112.105419-1-dave@stgolabs.net/):
>>>  - Validate the event vendor ID for CRB filtering, the Table 13-5
>>>    event groups are scoped by the CXL VID in patch 3 (Richard).
>>>  - Add Richard's Reviewed-by tag to patch 1.
>>>
>>> Three patches for the CXL PMU driver.
>>>
>>> Patch 1 is a standalone fix.
>>>
>>> Patch 2 adds the CXL 4.0 events that hardware exposes but the
>>> driver did not. It now precedes the filter work as the latter
>>> refers to the new event group IDs.
>>>
>>> Patch 3 implements Channel/Rank/Bank (CRB) filtering, now permitted
>>> for all event groups that CXL 4.0 Table 13-5 allows Filter ID 1 on.
>>>
>>> v2 was tested on real hardware. The v4 changes have been exercised
>>> under qemu CPMU emulation (jic23 tree) + changes for the new events/Filter=1:
>>>
>>>     https://lore.kernel.org/all/20260715190050.458288-1-dave@stgolabs.net/
>>>
>>> Thanks!
>>>
>>> Davidlohr Bueso (1):
>>>   perf/cxlpmu: Fix 64-bit write to 32-bit HDM filter register
>>>
>>> Harshal Thakkar (2):
>>>   perf/cxlpmu: Add missing CXL 4.0 events
>>>   perf/cxlpmu: Support Channel/Rank/Bank filter
>>>
>>>  drivers/perf/cxl_pmu.c | 119 +++++++++++++++++++++++++++++++++++++++--
>>>  1 file changed, 116 insertions(+), 3 deletions(-)
>>>
>>>
>>> base-commit: d60ec36cab338dfe2ae40d73e9c8d6c4af70d2b8
>>
>> For the series
>> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
>>
>>
>> This is being picked up by the perf maintainer right?
> 
> Yeah, I'll grab it eventually. Just a bit swamped atm.

Thanks Will! Wasn't trying to rush you. Just checking to see which acceptance path the series is going through.

> 
> Will


      reply	other threads:[~2026-07-16 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 19:14 [PATCH v4 0/3] perf/cxlpmu: Misc updates Davidlohr Bueso
2026-07-15 19:14 ` [PATCH v4 1/3] perf/cxlpmu: Fix 64-bit write to 32-bit HDM filter register Davidlohr Bueso
2026-07-15 20:07   ` sashiko-bot
2026-07-15 19:14 ` [PATCH v4 2/3] perf/cxlpmu: Add missing CXL 4.0 events Davidlohr Bueso
2026-07-16  6:32   ` Richard Cheng
2026-07-15 19:14 ` [PATCH v4 3/3] perf/cxlpmu: Support Channel/Rank/Bank filter Davidlohr Bueso
2026-07-16  6:53   ` Richard Cheng
2026-07-16 16:46 ` [PATCH v4 0/3] perf/cxlpmu: Misc updates Dave Jiang
2026-07-16 16:47   ` Will Deacon
2026-07-16 17:05     ` Dave Jiang [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=f7dfe837-a044-4d2e-bdb6-599157063eef@intel.com \
    --to=dave.jiang@intel.com \
    --cc=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