Linux CXL
 help / color / mirror / Atom feed
From: Shiju Jose <shiju.jose@huawei.com>
To: "mchehab@kernel.org" <mchehab@kernel.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
	Linuxarm <linuxarm@huawei.com>
Subject: RE: [PATCH V6 0/4] rasdaemon: Add support for the CXL error events
Date: Fri, 28 Apr 2023 17:59:34 +0000	[thread overview]
Message-ID: <c49dd10e62ae4e3d8850c119bba70523@huawei.com> (raw)
In-Reply-To: <20230331134404.1315-1-shiju.jose@huawei.com>

Hi All,

Pull request has submitted for this series.
https://github.com/mchehab/rasdaemon/pull/96

Thanks,
Shiju

-----Original Message-----
From: Shiju Jose <shiju.jose@huawei.com> 
Sent: 31 March 2023 14:44
To: mchehab@kernel.org; linux-cxl@vger.kernel.org; linux-edac@vger.kernel.org
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>; Linuxarm <linuxarm@huawei.com>; Shiju Jose <shiju.jose@huawei.com>
Subject: [PATCH V6 0/4] rasdaemon: Add support for the CXL error events

From: Shiju Jose <shiju.jose@huawei.com>

Log and record the following CXL error records reported through the kernel trace events. CXL poison errors, CXL AER uncorrectable errors and CXL AER correctable errors.

Shiju Jose (4):
  rasdaemon: Move definition for BIT and BIT_ULL to a common file
  rasdaemon: Add support for the CXL poison events
  rasdaemon: Add support for the CXL AER uncorrectable errors
  rasdaemon: Add support for the CXL AER correctable errors

Changes:
V5 -> V6
1. Following modification in the CXL poison due to
   changes in the kernel patches for the cxl_poison.
  - length -> dpa_length
  - add field trace_type
  
V4 -> V5
1. Add logging of device serial number for the CXL AER uncorrectable and
    CXL AER correctable errors.
2. Rebased.
3. Updated the patches description.	

V3 -> V4
1. Modification for the changes in the kernel patches
   a) https://lore.kernel.org/lkml/cover.1675983077.git.alison.schofield@intel.com/
   b) https://lore.kernel.org/linux-cxl/63e5ed38d77d9_138fbc2947a@iweiny-mobl.notmuch/T/#t

V2 -> V3
1. Fix for the comments from Dave Jiang.

RFC V1 -> V2
1. Rename uuid to region_uuid in the log and SQLite DB.
2. Rebase to the latest rasdaemon code.
3. Modify to match the name changes of interface structures and
   functions in the latest libtraceevent-dev, use in the rasdaemon. 

 Makefile.am                |   7 +-
 configure.ac               |  11 +
 ras-cxl-handler.c          | 426 +++++++++++++++++++++++++++++++++++++
 ras-cxl-handler.h          |  32 +++
 ras-events.c               |  33 +++
 ras-events.h               |   3 +
 ras-non-standard-handler.h |   3 -
 ras-record.c               | 215 +++++++++++++++++++
 ras-record.h               |  55 +++++
 ras-report.c               | 231 ++++++++++++++++++++
 ras-report.h               |   6 +
 11 files changed, 1018 insertions(+), 4 deletions(-)  create mode 100644 ras-cxl-handler.c  create mode 100644 ras-cxl-handler.h

--
2.25.1


      parent reply	other threads:[~2023-04-28 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 13:44 [PATCH V6 0/4] rasdaemon: Add support for the CXL error events shiju.jose
2023-03-31 13:44 ` [PATCH V6 1/4] rasdaemon: Move definition for BIT and BIT_ULL to a common file shiju.jose
2023-03-31 13:44 ` [PATCH V6 2/4] rasdaemon: Add support for the CXL poison events shiju.jose
2023-03-31 13:44 ` [PATCH V6 3/4] rasdaemon: Add support for the CXL AER uncorrectable errors shiju.jose
2023-03-31 13:44 ` [PATCH V6 4/4] rasdaemon: Add support for the CXL AER correctable errors shiju.jose
2023-04-28 17:59 ` 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=c49dd10e62ae4e3d8850c119bba70523@huawei.com \
    --to=shiju.jose@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox