From: Shiju Jose <shiju.jose@huawei.com>
To: Dave Jiang <dave.jiang@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"alison.schofield@intel.com" <alison.schofield@intel.com>,
"nifan.cxl@gmail.com" <nifan.cxl@gmail.com>,
"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
"ira.weiny@intel.com" <ira.weiny@intel.com>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
tanxiaofei <tanxiaofei@huawei.com>,
"Zengtao (B)" <prime.zeng@hisilicon.com>
Subject: RE: [PATCH v5 0/6] Update Event Records to CXL spec rev 3.1
Date: Sat, 11 Jan 2025 09:22:59 +0000 [thread overview]
Message-ID: <5a341e845e354c90ba699657dc0cbb86@huawei.com> (raw)
In-Reply-To: <ba35a66c-2dcc-4bb6-a0bb-163f4209449e@intel.com>
>-----Original Message-----
>From: Dave Jiang <dave.jiang@intel.com>
>Sent: 10 January 2025 20:18
>To: Shiju Jose <shiju.jose@huawei.com>; Jonathan Cameron
><jonathan.cameron@huawei.com>
>Cc: dan.j.williams@intel.com; alison.schofield@intel.com; nifan.cxl@gmail.com;
>vishal.l.verma@intel.com; ira.weiny@intel.com; dave@stgolabs.net; linux-
>cxl@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
><linuxarm@huawei.com>; tanxiaofei <tanxiaofei@huawei.com>; Zengtao (B)
><prime.zeng@hisilicon.com>
>Subject: Re: [PATCH v5 0/6] Update Event Records to CXL spec rev 3.1
>
>
>
>On 1/10/25 9:46 AM, Shiju Jose wrote:
>>> -----Original Message-----
>>> From: Jonathan Cameron <jonathan.cameron@huawei.com>
>>> Sent: 10 January 2025 16:07
>>> To: Shiju Jose <shiju.jose@huawei.com>
>>> Cc: dave.jiang@intel.com; dan.j.williams@intel.com;
>>> alison.schofield@intel.com; nifan.cxl@gmail.com;
>>> vishal.l.verma@intel.com; ira.weiny@intel.com; dave@stgolabs.net;
>>> linux-cxl@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
>>> <linuxarm@huawei.com>; tanxiaofei <tanxiaofei@huawei.com>; Zengtao
>>> (B) <prime.zeng@hisilicon.com>
>>> Subject: Re: [PATCH v5 0/6] Update Event Records to CXL spec rev 3.1
>>>
>>> On Fri, 10 Jan 2025 11:55:50 +0000
>>> <shiju.jose@huawei.com> wrote:
>>>
>>>> From: Shiju Jose <shiju.jose@huawei.com>
>>>>
>>>> Add updates in the CXL events records and CXL trace events
>>>> implementations for the changes in CXL spec rev 3.1.
>>>>
>>>> Shiju Jose (6):
>>>> cxl/events: Update Common Event Record to CXL spec rev 3.1
>>>> cxl/events: Add Component Identifier formatting for CXL spec rev 3.1
>>>> cxl/events: Update General Media Event Record to CXL spec rev 3.1
>>>> cxl/events: Update DRAM Event Record to CXL spec rev 3.1
>>>> cxl/events: Update Memory Module Event Record to CXL spec rev 3.1
>>>> cxl/test: Update test code for event records to CXL spec rev 3.1
>>>>
>>>> Changes:
>>>> V4 -> V5
>>>> 1. Reverted changes made in v4 for overcoming parsing error when
>>>> libtraceevent in userspace parses the CXL trace events, for rasdaemon.
>>>> This was due to trace event's format file is larger than PAGE_SIZE,
>>>> not supported reading complete format file in one go in the kernel
>>>> and thus fixed in the rasdaemon.
>>>
>>> Great to see that resolved.
>>>
>>>> 2. Rebased to v6.13-rc5.
>>>
>>> Should probably say why when doing a rebase to something other than rc1.
>>> In this case this is what cxl.git/next is based on after some fixes
>>> earlier in the cycle so a sensible choice for this set.
>>
>> I checked. These patches applied cleanly in cxl.git/next and buid okay.
>
>Hi Shiju,
>Can you please apply Ira's suggestions and respin a v6? Thanks!
Hi Dave,
Sure. I added Ira's suggestions and please find v6 of the series here.
https://lore.kernel.org/all/20250111091756.1682-1-shiju.jose@huawei.com/
Thanks,
Shiju
>
[...]
>
prev parent reply other threads:[~2025-01-11 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 11:55 [PATCH v5 0/6] Update Event Records to CXL spec rev 3.1 shiju.jose
2025-01-10 11:55 ` [PATCH v5 1/6] cxl/events: Update Common Event Record " shiju.jose
2025-01-10 17:35 ` Ira Weiny
2025-01-10 11:55 ` [PATCH v5 2/6] cxl/events: Add Component Identifier formatting for " shiju.jose
2025-01-10 17:43 ` Ira Weiny
2025-01-10 11:55 ` [PATCH v5 3/6] cxl/events: Update General Media Event Record to " shiju.jose
2025-01-10 17:54 ` Ira Weiny
2025-01-10 18:30 ` Ira Weiny
2025-01-10 11:55 ` [PATCH v5 4/6] cxl/events: Update DRAM " shiju.jose
2025-01-10 18:27 ` Ira Weiny
2025-01-11 9:16 ` Shiju Jose
2025-01-10 11:55 ` [PATCH v5 5/6] cxl/events: Update Memory Module " shiju.jose
2025-01-10 18:46 ` Ira Weiny
2025-01-10 11:55 ` [PATCH v5 6/6] cxl/test: Update test code for event records " shiju.jose
2025-01-10 18:48 ` Ira Weiny
2025-01-10 16:06 ` [PATCH v5 0/6] Update Event Records " Jonathan Cameron
2025-01-10 16:46 ` Shiju Jose
2025-01-10 20:18 ` Dave Jiang
2025-01-11 9:22 ` Shiju Jose [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=5a341e845e354c90ba699657dc0cbb86@huawei.com \
--to=shiju.jose@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=nifan.cxl@gmail.com \
--cc=prime.zeng@hisilicon.com \
--cc=tanxiaofei@huawei.com \
--cc=vishal.l.verma@intel.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