[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170322132934.12ca83c4@roar.ozlabs.ibm.com>
Date: Wed, 22 Mar 2017 13:29:34 +1000
From: Nicholas Piggin <npiggin@...il.com>
To: "Gautham R. Shenoy" <ego@...ux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Michael Neuling <mikey@...ling.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
"Shreyas B. Prabhu" <shreyasbp@...il.com>,
Shilpasri G Bhat <shilpa.bhat@...ux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Anton Blanchard <anton@...ba.org>,
Balbir Singh <bsingharora@...il.com>,
Akshay Adiga <akshay.adiga@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [v2 PATCH 4/4] powernv: Recover correct PACA on wakeup from a
stop on P9 DD1
On Tue, 21 Mar 2017 02:59:46 +1000
Nicholas Piggin <npiggin@...il.com> wrote:
> On Mon, 20 Mar 2017 21:24:18 +0530
> This is quite neat now you've moved it to its own function. Nice.
> It will be only a trivial clash with my patches now, I think.
>
> Reviewed-by: Nicholas Piggin <npiggin@...il.com>
Hmm... This won't actually work for machine check wakeups either.
We're doing the low level machine check before checking for wakeup,
which complicates things a little bit.
Simplest way to handle that might be to just always immediately
call the restore paca function at machine check entry, and then
just always mark machine checks as not-recoverable for DD1.
Thanks,
Nick
Powered by blists - more mailing lists