public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: Nicholas Piggin <npiggin@gmail•com>
To: linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>,
	Michael Ellerman <mpe@ellerman•id.au>,
	Mahesh Salgaonkar <mahesh@linux•vnet.ibm.com>
Subject: [PATCH 0/3 v2] MCE handler for POWER9
Date: Tue, 28 Feb 2017 12:00:45 +1000	[thread overview]
Message-ID: <20170228020048.8862-1-npiggin@gmail.com> (raw)

Hi,

This is a minimal implementation of the POWER9 MCE handler that
should be suitable for backport if necessary.

Moving this to firmware may be the right long term solution, but
we need a P9 Linux handler for existing kernels and firmwares.

Thanks,
Nick

Nicholas Piggin (3):
  powerpc/64s: fix handling of non-synchronous machine checks
  powerpc/64s: allow machine check handler to set severity and initiator
  powerpc/64s: POWER9 machine check handler

 arch/powerpc/include/asm/bitops.h     |   4 +
 arch/powerpc/include/asm/mce.h        | 108 +++++++++++++++-
 arch/powerpc/kernel/cputable.c        |   3 +
 arch/powerpc/kernel/mce.c             |  88 ++++++++++++-
 arch/powerpc/kernel/mce_power.c       | 237 ++++++++++++++++++++++++++++++++++
 arch/powerpc/platforms/powernv/opal.c |  21 +--
 6 files changed, 443 insertions(+), 18 deletions(-)

-- 
2.11.0

next             reply	other threads:[~2017-02-28  2:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  2:00 Nicholas Piggin [this message]
2017-02-28  2:00 ` [PATCH 1/3] powerpc/64s: fix handling of non-synchronous machine checks Nicholas Piggin
2017-02-28  5:57   ` Mahesh Jagannath Salgaonkar
2017-02-28  8:43     ` Nicholas Piggin
2017-03-14 11:45   ` [1/3] " Michael Ellerman
2017-02-28  2:00 ` [PATCH 2/3] powerpc/64s: allow machine check handler to set severity and initiator Nicholas Piggin
2017-02-28  2:00 ` [PATCH 3/3] powerpc/64s: POWER9 machine check handler Nicholas Piggin
2017-02-28  7:07   ` Mahesh Jagannath Salgaonkar
2017-03-09  5:35     ` 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=20170228020048.8862-1-npiggin@gmail.com \
    --to=npiggin@gmail$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mahesh@linux$(echo .)vnet.ibm.com \
    --cc=mpe@ellerman$(echo .)id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox