From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <linux-edac@vger.kernel.org>
Cc: <mchehab@kernel.org>, <linuxarm@huawei.com>, <jcm@redhat.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: [RFC PATCH 0/6] CCIX rasdaemon support
Date: Sat, 15 Jun 2019 01:55:11 +0800 [thread overview]
Message-ID: <20190614175517.58442-1-Jonathan.Cameron@huawei.com> (raw)
This is an RFC because the kernel side is currently under review and
may change with obvious follow through effects on this.
https://lore.kernel.org/linux-edac/20190606123654.78973-1-Jonathan.Cameron@huawei.com/
There are a few additional questions around this:
1. Divide between specifity of DB fields vs blobs.
Where possible I have tried to fully describe the contents via
separate fields rather than large blobs. One common SQL convention
that doesn't seem to have been previously done in rasdaemon is to
use explicit NULL entries for elements where data is missing.
2. Should we split ras-record.c and have the ccix handling in a separate
ras-record-ccix.c file or similar as that one is getting rather large.
Note the following is a trademark grant and doesn't prevent normal
stuff covered under fair use. Given this doesn't current quote from
the spec, there are no such copyright notices.
This patch is being distributed by the CCIX Consortium, Inc. (CCIX) to
you and other parties that are paticipating (the "participants") in
rasdemon project with the understanding that the participants will use CCIX's
name and trademark only when this patch is used in association with
rasdaemon.
CCIX is also distributing this patch to these participants with the
understanding that if any portion of the CCIX specification will be
used or referenced in rasdaemon, the participants will not modify
the cited portion of the CCIX specification and will give CCIX propery
copyright attribution by including the following copyright notice with
the cited part of the CCIX specification:
"© 2019 CCIX CONSORTIUM, INC. ALL RIGHTS RESERVED."
Jonathan Cameron (6):
rasdaemon: CCIX: CCIX memory error reporting.
rasdaemon: CCIX: Cache error support
rasdaemon: CCIX: ATC errors
rasdaemon: CCIX: Port error handling
rasdaemon: CCIX: Link error support
rasdaemon: CCIX: Agent Internal error support
Makefile.am | 6 +-
configure.ac | 10 +
ras-ccix-handler.c | 648 +++++++++++++++++++++++++++++++++++++++++++++
ras-ccix-handler.h | 139 ++++++++++
ras-events.c | 61 +++++
ras-record.c | 568 +++++++++++++++++++++++++++++++++++++++
ras-record.h | 35 +++
ras-report.h | 6 +-
8 files changed, 1471 insertions(+), 2 deletions(-)
create mode 100644 ras-ccix-handler.c
create mode 100644 ras-ccix-handler.h
--
2.20.1
next reply other threads:[~2019-06-14 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:55 Jonathan Cameron [this message]
2019-06-14 17:55 ` [RFC PATCH 1/6] rasdaemon: CCIX: CCIX memory error reporting Jonathan Cameron
2019-06-14 17:55 ` [RFC PATCH 2/6] rasdaemon: CCIX: Cache error support Jonathan Cameron
2019-06-14 17:55 ` [RFC PATCH 3/6] rasdaemon: CCIX: ATC errors Jonathan Cameron
2019-06-14 17:55 ` [RFC PATCH 4/6] rasdaemon: CCIX: Port error handling Jonathan Cameron
2019-06-14 17:55 ` [RFC PATCH 5/6] rasdaemon: CCIX: Link error support Jonathan Cameron
2019-06-14 17:55 ` [RFC PATCH 6/6] rasdaemon: CCIX: Agent Internal " Jonathan Cameron
2019-06-21 18:56 ` [RFC PATCH 0/6] CCIX rasdaemon support Mauro Carvalho Chehab
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=20190614175517.58442-1-Jonathan.Cameron@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jcm@redhat.com \
--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).