linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <shiju.jose@huawei.com>
To: <mchehab@kernel.org>, <linux-cxl@vger.kernel.org>,
	<linux-edac@vger.kernel.org>
Cc: <jonathan.cameron@huawei.com>, <linuxarm@huawei.com>,
	<shiju.jose@huawei.com>
Subject: [RFC PATCH 0/7] rasdaemon: Process the generic CXL trace events
Date: Wed, 12 Apr 2023 16:33:04 +0800	[thread overview]
Message-ID: <20230412083312.1384-1-shiju.jose@huawei.com> (raw)

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

Log and record the following generic CXL error records reported through
the kernel trace events.
- cxl_overflow
- cxl_generic_event
- cxl_general_media
- cxl_dram
- cxl_memory_module

Shiju Jose (7):
  rasdaemon: Add common function to convert timestamp in the CXL event
    records to the broken-down time format
  rasdaemon: Add common function to get timestamp for the event
  rasdaemon: Add support for the CXL overflow events
  rasdaemon: Add support for the CXL generic events
  rasdaemon: Add support for the CXL general media events
  rasdaemon: Add support for the CXL dram events
  rasdaemon: Add support for the CXL memory module events

 ras-cxl-handler.c | 826 +++++++++++++++++++++++++++++++++++++++++++---
 ras-cxl-handler.h |  15 +
 ras-events.c      |  45 +++
 ras-events.h      |   5 +
 ras-record.c      | 420 +++++++++++++++++++++++
 ras-record.h      |  99 ++++++
 ras-report.c      | 476 ++++++++++++++++++++++++++
 ras-report.h      |  10 +
 8 files changed, 1853 insertions(+), 43 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-04-12  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  8:33 shiju.jose [this message]
2023-04-12  8:33 ` [RFC PATCH 1/7] rasdaemon: Add common function to convert timestamp in the CXL event records to the broken-down time format shiju.jose
2023-04-12  8:33 ` [RFC PATCH 2/7] rasdaemon: Add common function to get timestamp for the event shiju.jose
2023-04-12  8:33 ` [RFC PATCH 3/7] rasdaemon: Add support for the CXL overflow events shiju.jose
2023-04-12  8:33 ` [RFC PATCH 4/7] rasdaemon: Add support for the CXL generic events shiju.jose
2023-04-12  8:33 ` [RFC PATCH 5/7] rasdaemon: Add support for the CXL general media events shiju.jose
2023-04-12  8:33 ` [RFC PATCH 6/7] rasdaemon: Add support for the CXL dram events shiju.jose
2023-04-12  8:33 ` [RFC PATCH 7/7] rasdaemon: Add support for the CXL memory module events 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=20230412083312.1384-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).