From: Nicholas Piggin <npiggin@gmail•com>
To: linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>
Subject: [PATCH 0/6] table-based machine check handlers
Date: Tue, 14 Mar 2017 22:36:42 +1000 [thread overview]
Message-ID: <20170314123648.26068-1-npiggin@gmail.com> (raw)
Hi,
This is a rebase of the table based MCE patches on top of the POWER9
handler that was merged upstream. Plus a couple of misc things (patches
1 and 6).
The plan is to have OPAL firmware do most of this recovery and parsing
in future, but I think it's worth tidying this up. IMO it's easier to
see what's going on and less error prone to change or add things.
Thanks,
Nick
Nicholas Piggin (6):
powerpc/64s: machine check print NIP
powerpc/64s: clean up machine check recovery flushing
powerpc/64s: move POWER machine check defines into mce_power.c
powerpc/64s: data driven machine check evaluation
powerpc/64s: data driven machine check handling
powerpc/64s: POWER8 add missing machine check definitions
arch/powerpc/include/asm/mce.h | 91 -----
arch/powerpc/kernel/mce.c | 3 +-
arch/powerpc/kernel/mce_power.c | 776 +++++++++++++++++++---------------------
3 files changed, 369 insertions(+), 501 deletions(-)
--
2.11.0
next reply other threads:[~2017-03-14 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 12:36 Nicholas Piggin [this message]
2017-03-14 12:36 ` [PATCH 1/6] powerpc/64s: machine check print NIP Nicholas Piggin
2017-03-21 11:36 ` [1/6] " Michael Ellerman
2017-03-14 12:36 ` [PATCH 2/6] powerpc/64s: clean up machine check recovery flushing Nicholas Piggin
2017-03-14 12:36 ` [PATCH 3/6] powerpc/64s: move POWER machine check defines into mce_power.c Nicholas Piggin
2017-03-14 12:36 ` [PATCH 4/6] powerpc/64s: data driven machine check evaluation Nicholas Piggin
2017-03-14 12:36 ` [PATCH 5/6] powerpc/64s: data driven machine check handling Nicholas Piggin
2017-03-14 12:36 ` [PATCH 6/6] powerpc/64s: POWER8 add missing machine check definitions Nicholas Piggin
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=20170314123648.26068-1-npiggin@gmail.com \
--to=npiggin@gmail$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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