From: Balbir Singh <bsingharora@gmail.com>
To: npiggin@gmail.com, mahesh@linux.vnet.ibm.com, alistair@popple.id.au
Cc: linuxppc-dev@ozlabs.org, Balbir Singh <bsingharora@gmail.com>
Subject: [rfc 0/3] Revisit MCE handling for UE errors
Date: Tue, 5 Sep 2017 14:15:52 +1000 [thread overview]
Message-ID: <20170905041555.27696-1-bsingharora@gmail.com> (raw)
This patch series is designed to hook up memory_failure on
UE errors, this is specially helpful for user_mode UE errors.
The first patch is a cleanup patch, it removes dead code.
I could not find any users of get_mce_fault_addr().
The second patch walks kernel/user mode page tables in
real mode to extract the effective address of the instruction
that caused the UE error and the effective address it was
trying to access (for load/store).
The third patch hooks up memory_failure to the MCE patch.
TODO:
Log the address in NVRAM, so that we can recover from
bad pages at boot and keep the blacklist persistent.
Balbir Singh (3):
powerpc/mce.c: Remove unused function get_mce_fault_addr()
powerpc/mce: Extract physical_address for UE errors
powerpc/mce: hookup memory_failure for UE errors
arch/powerpc/include/asm/mce.h | 4 +-
arch/powerpc/kernel/mce.c | 107 ++++++++++++++++++++++++----------------
arch/powerpc/kernel/mce_power.c | 60 ++++++++++++++++++++--
3 files changed, 120 insertions(+), 51 deletions(-)
--
2.9.5
next reply other threads:[~2017-09-05 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 4:15 Balbir Singh [this message]
2017-09-05 4:15 ` [rfc 1/3] powerpc/mce.c: Remove unused function get_mce_fault_addr() Balbir Singh
2017-09-05 4:15 ` [rfc 2/3] powerpc/mce: Extract physical_address for UE errors Balbir Singh
2017-09-06 0:36 ` Nicholas Piggin
2017-09-06 4:37 ` Balbir Singh
2017-09-06 22:56 ` Benjamin Herrenschmidt
2017-09-07 1:52 ` Balbir Singh
2017-09-08 3:41 ` Mahesh Jagannath Salgaonkar
2017-09-05 4:15 ` [rfc 3/3] powerpc/mce: hookup memory_failure " Balbir Singh
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=20170905041555.27696-1-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=alistair@popple.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=npiggin@gmail.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).