All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: [RFC[PATCH 0/4] POWER9 machine check handler
Date: Fri, 17 Feb 2017 03:01:10 +1000	[thread overview]
Message-ID: <20170216170114.25247-1-npiggin@gmail.com> (raw)

So far I've only got this tested in mambo simulator, but
some recoverable and unrecoverable events seem to work.

Thanks,
Nick

Nicholas Piggin (4):
  powerpc: machine check allow handler to set severity and initiator
  powerpc/powernv: machine check rework recovery flushing
  powerpc/powernv: cope with non-synchronous machine checks
  powerpc/powernv: handle POWER9 machine checks

 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             |  90 +++++++++-
 arch/powerpc/kernel/mce_power.c       | 324 +++++++++++++++++++++++++++-------
 arch/powerpc/platforms/powernv/opal.c |  19 +-
 6 files changed, 465 insertions(+), 83 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-02-16 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 17:01 Nicholas Piggin [this message]
2017-02-16 17:01 ` [PATCH 1/4] powerpc: machine check allow handler to set severity and initiator Nicholas Piggin
2017-02-16 17:01 ` [PATCH 2/4] powerpc/powernv: machine check rework recovery flushing Nicholas Piggin
2017-02-16 17:01 ` [PATCH 3/4] powerpc/powernv: cope with non-synchronous machine checks Nicholas Piggin
2017-02-17  0:04   ` kbuild test robot
2017-02-16 17:01 ` [PATCH 4/4] powerpc/powernv: handle POWER9 " Nicholas Piggin
2017-02-16 21:15   ` kbuild test robot
2017-02-17  0:36   ` kbuild test robot
2017-02-16 17:47 ` [RFC[PATCH 0/4] POWER9 machine check handler 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=20170216170114.25247-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.