From: Shiju Jose <shiju.jose@huawei.com>
To: <linux-edac@vger.kernel.org>, <mchehab+huawei@kernel.org>
Cc: <linuxarm@openeuler.org>, <tanxiaofei@huawei.com>,
<jonathan.cameron@huawei.com>
Subject: [PATCH v2 0/8] rasdaemon: add support for memory_failure events,
Date: Mon, 25 Jan 2021 17:14:47 +0000 [thread overview]
Message-ID: <20210125171455.1886-1-shiju.jose@huawei.com> (raw)
Add support for the memory_failure trace event in the rasdaemon and
add improvements & support for the vendor specific errors in the
util/ras-mc-ctl.in.
Changes:
v1 -> v2
1. Fix the feedback by Mauro for the fix patch for the exception
in the ras-mc-ctl.in.
2. Rebased and grouped the previous v1 rasdaemon patches posted.
Shiju Jose (8):
rasdaemon: add support for memory_failure events
rasdaemon: ras-mc-ctl: Modify ARM processor error summary log
rasdaemon: ras-mc-ctl: Add memory failure events
rasdaemon: ras-mc-ctl: Fix for exception when an event is not enabled
rasdaemon: ras-mc-ctl: Add support for the vendor-specific errors
rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng920 errors
rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng9xx common
errors
rasdaemon: Modify confiure.ac for Hisilicon Kunpeng errors
.travis.yml | 2 +-
Makefile.am | 7 +-
configure.ac | 20 +-
ras-events.c | 15 +
ras-events.h | 1 +
ras-memory-failure-handler.c | 179 +++++++++
ras-memory-failure-handler.h | 25 ++
ras-record.c | 70 ++++
ras-record.h | 13 +
ras-report.c | 68 ++++
ras-report.h | 2 +
util/ras-mc-ctl.in | 737 +++++++++++++++++++++++++----------
12 files changed, 927 insertions(+), 212 deletions(-)
create mode 100644 ras-memory-failure-handler.c
create mode 100644 ras-memory-failure-handler.h
--
2.17.1
next reply other threads:[~2021-01-25 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 17:14 Shiju Jose [this message]
2021-01-25 17:14 ` [PATCH v2 1/8] rasdaemon: add support for memory_failure events Shiju Jose
2021-01-25 17:14 ` [PATCH v2 2/8] rasdaemon: ras-mc-ctl: Modify ARM processor error summary log Shiju Jose
2021-01-25 17:14 ` [PATCH v2 3/8] rasdaemon: ras-mc-ctl: Add memory failure events Shiju Jose
2021-01-25 17:14 ` [PATCH v2 4/8] rasdaemon: ras-mc-ctl: Fix for exception when an event is not enabled Shiju Jose
2021-01-25 17:14 ` [PATCH v2 5/8] rasdaemon: ras-mc-ctl: Add support for the vendor-specific errors Shiju Jose
2021-01-25 17:14 ` [PATCH v2 6/8] rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng920 errors Shiju Jose
2021-01-25 17:14 ` [PATCH v2 7/8] rasdaemon: ras-mc-ctl: Add support for HiSilicon Kunpeng9xx common errors Shiju Jose
2021-01-25 17:14 ` [PATCH v2 8/8] rasdaemon: Modify confiure.ac for Hisilicon Kunpeng 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=20210125171455.1886-1-shiju.jose@huawei.com \
--to=shiju.jose@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=mchehab+huawei@kernel.org \
--cc=tanxiaofei@huawei.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;
as well as URLs for NNTP newsgroup(s).