From: Shiju Jose <shiju.jose@huawei.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Linuxarm <linuxarm@huawei.com>
Subject: RE: [RESEND PATCH V3 2/4] rasdaemon: Add support for the CXL poison events
Date: Fri, 3 Feb 2023 09:31:11 +0000 [thread overview]
Message-ID: <a5df429552ea4c65b680f985daa32c29@huawei.com> (raw)
In-Reply-To: <Y9wR+Kqs1P65ztwT@aschofie-mobl2>
>-----Original Message-----
>From: Alison Schofield <alison.schofield@intel.com>
>Sent: 02 February 2023 19:42
>To: Shiju Jose <shiju.jose@huawei.com>
>Cc: mchehab@kernel.org; linux-edac@vger.kernel.org; linux-
>cxl@vger.kernel.org; Jonathan Cameron <jonathan.cameron@huawei.com>;
>Linuxarm <linuxarm@huawei.com>
>Subject: Re: [RESEND PATCH V3 2/4] rasdaemon: Add support for the CXL poison
>events
>
>On Thu, Feb 02, 2023 at 06:18:44PM +0000, shiju.jose@huawei.com wrote:
>> From: Shiju Jose <shiju.jose@huawei.com>
>>
>> Add support to log and record the CXL poison events.
>>
>> The corresponding Kernel patches here:
>> https://lore.kernel.org/linux-cxl/de11785ff05844299b40b100f8e0f56c7eef
>> 7f08.1674070170.git.alison.schofield@intel.com/
>>
>> Presently RFC draft version for logging, could be extended for the
>> policy based recovery action for the frequent poison events depending
>> on the above kernel patches.
>
>Hi Shiju,
>
>Looks good to me based on the kernel patches you reference above.
>I want to let you know that a v6 is in the works, and will lead to some naming
>changes below - but minor stuff.
Hi Alison,
Thanks for the information. I will make changes according to the v6.
>
>Alison
>
Thanks,
Shiju
next prev parent reply other threads:[~2023-02-03 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 18:18 [RESEND PATCH V3 0/4] rasdaemon: Add support for the CXL error events shiju.jose
2023-02-02 18:18 ` [RESEND PATCH V3 1/4] rasdaemon: Move definition for BIT and BIT_ULL to a common file shiju.jose
2023-02-02 18:18 ` [RESEND PATCH V3 2/4] rasdaemon: Add support for the CXL poison events shiju.jose
2023-02-02 19:41 ` Alison Schofield
2023-02-03 9:31 ` Shiju Jose [this message]
2023-02-02 18:18 ` [RESEND PATCH V3 3/4] rasdaemon: Add support for the CXL AER uncorrectable errors shiju.jose
2023-02-02 18:18 ` [RESEND PATCH V3 4/4] rasdaemon: Add support for the CXL AER correctable errors shiju.jose
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=a5df429552ea4c65b680f985daa32c29@huawei.com \
--to=shiju.jose@huawei.com \
--cc=alison.schofield@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.