From: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: [PATCH 0/2] powerpc/powernv: Plumb fsp memory errors to memory poison infrastructure.
Date: Fri, 15 Nov 2013 09:50:43 +0530 [thread overview]
Message-ID: <20131115041952.5748.19640.stgit@mars.in.ibm.com> (raw)
Hi,
Please find the patch set that implements FSP memory error handling and
plumbs then into memory poison infrastructure.
Patch 1 enables the generic memory hwpoisoning infrastructure for ppc64.
Patch 2 reads the memory errors reported from opal layer and plumbs them
into memory poison infrastructure.
This patch uses new messaging channel infrastructure (proposed through a
separate patch at
https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-November/113331.html)
to pull the fsp memory errors to linux.
Thanks,
-Mahesh.
---
Mahesh Salgaonkar (2):
powerpc/powernv: Add config option for hwpoisoning.
powerpc/powernv: Get FSP memory errors and plumb into memory poison infrastructure.
arch/powerpc/Kconfig | 6 +
arch/powerpc/include/asm/opal.h | 52 +++++++
arch/powerpc/platforms/powernv/Makefile | 1
.../powerpc/platforms/powernv/opal-memory-errors.c | 146 ++++++++++++++++++++
4 files changed, 205 insertions(+)
create mode 100644 arch/powerpc/platforms/powernv/opal-memory-errors.c
--
-Mahesh
next reply other threads:[~2013-11-15 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 4:20 Mahesh J Salgaonkar [this message]
2013-11-15 4:20 ` [PATCH 1/2] powerpc/powernv: Add config option for hwpoisoning Mahesh J Salgaonkar
2013-11-15 4:20 ` [PATCH 2/2] powerpc/powernv: Get FSP memory errors and plumb into memory poison infrastructure Mahesh J Salgaonkar
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=20131115041952.5748.19640.stgit@mars.in.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).