From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Edac Mailing List <linux-edac@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC EDAC/GHES 0/3] Add EDAC support on GHES
Date: Wed, 31 Oct 2012 15:44:52 -0200 [thread overview]
Message-ID: <cover.1351705248.git.mchehab@redhat.com> (raw)
It turns that making ghes to talk with EDAC to not be a hard
task.
This patch series makes ghes->edac integration.
This was compile-tested only, as its, for now, just a proof of
concept.
There are lots of space for improvements, like:
- maybe split edac-ghes into a separate file;
- add a way to retrieve the DIMM label (not sure if APEI GHES
interface supports it);
- detect the memory layout via ACPI;
Comments, sugestions etc are welcome.
Mauro Carvalho Chehab (3):
ghes: Be a good citzen with EDAC
edac: add support for raw error reports
ghes: add support for reporting errors via EDAC
drivers/acpi/apei/Kconfig | 1 +
drivers/acpi/apei/Makefile | 2 +
drivers/acpi/apei/ghes.c | 129 +++++++++++++++++++++++++++++++++++++++++++--
drivers/edac/edac_core.h | 17 ++++++
drivers/edac/edac_mc.c | 109 ++++++++++++++++++++++++++++----------
include/linux/edac.h | 5 ++
6 files changed, 233 insertions(+), 30 deletions(-)
--
1.7.11.7
next reply other threads:[~2012-10-31 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 17:44 Mauro Carvalho Chehab [this message]
2012-10-31 17:44 ` [RFC EDAC/GHES 1/3] ghes: Be a good citzen with EDAC Mauro Carvalho Chehab
2012-10-31 17:44 ` [RFC EDAC/GHES 2/3] edac: add support for raw error reports Mauro Carvalho Chehab
2012-10-31 17:44 ` [RFC EDAC/GHES 3/3] ghes: add support for reporting errors via EDAC 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=cover.1351705248.git.mchehab@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome