From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>, linuxppc-dev@lists•ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail•com>,
Mahesh Salgaonkar <mahesh@linux•vnet.ibm.com>
Subject: Re: [1/3] powerpc/64s: fix handling of non-synchronous machine checks
Date: Tue, 14 Mar 2017 22:45:56 +1100 (AEDT) [thread overview]
Message-ID: <3vjCc45Fp9z9s3l@ozlabs.org> (raw)
In-Reply-To: <20170228020048.8862-2-npiggin@gmail.com>
On Tue, 2017-02-28 at 02:00:46 UTC, Nicholas Piggin wrote:
> A synchronous machine check is an exception raised by the attempt to
> execute the current instruction. If the error can't be corrected, it
> can make sense to SIGBUS the currently running process.
>
> In other cases, the error condition is not related to the current
> instruction, so killing the current process is not the right thing to
> do.
>
> Today, all machine checks are MCE_SEV_ERROR_SYNC, so this has no
> practical change. It will be used to handle POWER9 asynchronous
> machine checks.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Series applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/1363875bdb6317a2d0798284d7aaf3
cheers
next prev parent reply other threads:[~2017-03-14 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 2:00 [PATCH 0/3 v2] MCE handler for POWER9 Nicholas Piggin
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 ` Michael Ellerman [this message]
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=3vjCc45Fp9z9s3l@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mahesh@linux$(echo .)vnet.ibm.com \
--cc=npiggin@gmail$(echo .)com \
/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