From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Will Deacon <will@kernel.org>
Cc: Ira Weiny <ira.weiny@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>, <mark.rutland@arm.com>,
<dave.jiang@intel.com>, <alison.schofield@intel.com>,
<dan.j.williams@intel.com>, <fan.ni@samsung.com>,
<a.manzanares@samsung.com>, <linux-cxl@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] perf/cxlpmu: Support missing events in 3.1 spec
Date: Tue, 15 Oct 2024 17:55:23 +0100 [thread overview]
Message-ID: <20241015175523.00004d85@Huawei.com> (raw)
In-Reply-To: <20241014141551.GA17702@willie-the-truck>
On Mon, 14 Oct 2024 15:15:52 +0100
Will Deacon <will@kernel.org> wrote:
> On Fri, Oct 11, 2024 at 09:35:58AM -0500, Ira Weiny wrote:
> > Davidlohr Bueso wrote:
> > > Update the CXL PMU driver to support the new events introduced
> > > in the latest revision. These are:
> > >
> > > - read/write accesses with TEE constraints.
> > > - S2M indicating Modified state.
> > >
> > > Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > Just to be sure: Jonathan you are taking this through CPMU correct?
>
> I was about to pick it up via the perf tree, so I'll hold fire until we
> hear back from Jonathan.
>
> Will
>
Hi Will,
Please pick it up via the perf tree. That driver isn't big enough to warrant
separate handling and this stuff won't impact the CXL tree.
Thanks,
Jonathan
next prev parent reply other threads:[~2024-10-15 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 2:52 [PATCH v3] perf/cxlpmu: Support missing events in 3.1 spec Davidlohr Bueso
2024-10-11 14:35 ` Ira Weiny
2024-10-14 14:15 ` Will Deacon
2024-10-15 16:55 ` Jonathan Cameron [this message]
2024-10-24 12:25 ` Will Deacon
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=20241015175523.00004d85@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-cxl@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;
as well as URLs for NNTP newsgroup(s).