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>
Subject: Re: [1/2] powerpc/64s: Fix FIXUP_ENDIAN non-maskable interrupt reentrancy
Date: Tue, 30 May 2017 19:11:16 +1000 (AEST) [thread overview]
Message-ID: <3wcSX45V80z9s72@ozlabs.org> (raw)
In-Reply-To: <20170501120110.21888-2-npiggin@gmail.com>
On Mon, 2017-05-01 at 12:01:09 UTC, Nicholas Piggin wrote:
> FIXUP_ENDIAN uses SRR[01] with MSR_RI=1, which gets corrupted if there
> is an interleaving system reset or machine check interrupt.
>
> Set MSR_RI=0 before setting SRRs. The rfid will restore MSR.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/f1fe5252018075e18d7f0c0e23ee17
cheers
next prev parent reply other threads:[~2017-05-30 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 12:01 [PATCH 0/2] non maskable interrupt reentrancy fixes for OPAL Nicholas Piggin
2017-05-01 12:01 ` [PATCH 1/2] powerpc/64s: Fix FIXUP_ENDIAN non-maskable interrupt reentrancy Nicholas Piggin
2017-05-30 9:11 ` Michael Ellerman [this message]
2017-05-01 12:01 ` [PATCH 2/2] powerpc/64s: Fix OPAL_CALL " 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=3wcSX45V80z9s72@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).