From: Balbir Singh <bsingharora@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH][RFC] powerpc/64s: Use emergency stack for 0x100 system reset interrupt
Date: Fri, 14 Oct 2016 21:51:16 +1100 [thread overview]
Message-ID: <6e4b347e-2c59-ed0a-6012-c8e849f3ff29@gmail.com> (raw)
In-Reply-To: <20161013065106.5389-1-npiggin@gmail.com>
On 13/10/16 17:51, Nicholas Piggin wrote:
> Also use EX_NMI save space. This should give cleaner debug data in
> case kernel stacks have become corrupted.
>
> MSR_RI is kept clear for the 0x100 handler, because we can't mask it,
> and can't tolerate a reentrant NMI. Technically the 0x100 is not really
> recoverable yet, because it could trample on another emergency stack
> user. This will require a bit more work to safely implement, but for
> now we don't need to recover after a 0x100.
>
> A little bit of the emergency stack / MSR_RI handling differences seem
> like they can be consolidated with some other handlers. I'll split those
> into a couple more patches before submitting.
>
> I moved the MC save area in the paca out from between the general and
> slb save areas, and put it with the nmi area because it shouldn't be used
> much.
I think we should document the limitations as discussed
One of them is that sequential system resets have unpredictable behaviour
when done in quick successions. I also don't like some of the naming like
NORI, I would rather prefer NOT_RI, but thats just nit picking
Balbir Singh.
prev parent reply other threads:[~2016-10-14 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 6:51 [PATCH][RFC] powerpc/64s: Use emergency stack for 0x100 system reset interrupt Nicholas Piggin
2016-10-14 10:51 ` Balbir Singh [this message]
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=6e4b347e-2c59-ed0a-6012-c8e849f3ff29@gmail.com \
--to=bsingharora@gmail.com \
--cc=anton@samba.org \
--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).