linux-kernel - [RFC EDAC/GHES 0/3] Add EDAC support on GHES

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 31 Oct 2012 15:44:52 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [RFC EDAC/GHES 0/3] Add EDAC support on GHES

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/