linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <shiju.jose@huawei.com>
To: <mchehab@kernel.org>, <linux-edac@vger.kernel.org>,
	<linux-cxl@vger.kernel.org>
Cc: <jonathan.cameron@huawei.com>, <linuxarm@huawei.com>,
	<shiju.jose@huawei.com>
Subject: [RESEND PATCH V3 0/4] rasdaemon: Add support for the CXL error events
Date: Thu, 2 Feb 2023 18:18:42 +0000	[thread overview]
Message-ID: <20230202181846.692-1-shiju.jose@huawei.com> (raw)

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

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

Note1: This V3 patch set resend due to email delivery issues to
some of the recipients.


Note2: The default poll and read method in the rasdaemon to receive
the trace events do not work due to a commit in the kernel trace system.
Thus instead used the pthread way for testing the CXL error events.
To do so, please make following change in the ras-events.c
<change start ...>
/* rc = read_ras_event_all_cpus(data, cpus); */
rc = -255;
< ...change end >
/* Poll doesn't work on this kernel. Fallback to pthread way */
if (rc == -255) {
...

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:
RFC 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          | 378 +++++++++++++++++++++++++++++++++++++
 ras-cxl-handler.h          |  32 ++++
 ras-events.c               |  33 ++++
 ras-events.h               |   3 +
 ras-non-standard-handler.h |   3 -
 ras-record.c               | 203 ++++++++++++++++++++
 ras-record.h               |  49 +++++
 ras-report.c               | 219 +++++++++++++++++++++
 ras-report.h               |   6 +
 11 files changed, 940 insertions(+), 4 deletions(-)
 create mode 100644 ras-cxl-handler.c
 create mode 100644 ras-cxl-handler.h

-- 
2.25.1


             reply	other threads:[~2023-02-02 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 18:18 shiju.jose [this message]
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
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=20230202181846.692-1-shiju.jose@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;
as well as URLs for NNTP newsgroup(s).