[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1164070425.8073.40.camel@localhost.localdomain>
Date: Tue, 21 Nov 2006 11:53:44 +1100
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: cbe-oss-dev@...abs.org, linuxppc-dev@...abs.org,
Paul Mackerras <paulus@...ba.org>,
linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd.bergmann@...ibm.com>
Subject: Re: [PATCH 01/22] powerpc: convert idle_loop to use
hard_irq_disable()
I got a bug report that I believe might be fixed by this
patch. The problem seems to be that with soft-disabled
interrupts in power_save, we can still get external exceptions
on Cell, even if we are in pause(0) a.k.a. sleep state.
When the CPU really wakes up through the 0x100 (system reset)
vector, while we have already started processing the 0x500
(external) exception, we get a panic in unrecoverable_exception()
because of the lost state.
This occurred in Systemsim for Cell, but as far as I can see,
it can theoretically occur on any machine that uses the
system reset exception to get out of sleep state.
Signed-off-by: Benjamin Herrenschmidt <benh@...nel.crashing.org>
---
What about that patch instead ?
Index: linux-cell/arch/powerpc/platforms/cell/pervasive.c
===================================================================
--- linux-cell.orig/arch/powerpc/platforms/cell/pervasive.c 2006-11-21 11:01:12.000000000 +1100
+++ linux-cell/arch/powerpc/platforms/cell/pervasive.c 2006-11-21 11:48:12.000000000 +1100
@@ -41,6 +41,15 @@
static void cbe_power_save(void)
{
unsigned long ctrl, thread_switch_control;
+
+ /*
+ * We need to hard disable interrupts, but we also need to mark them
+ * hard disabled in the PACA so that the local_irq_enable() done by
+ * our caller upon return propertly hard enables.
+ */
+ hard_irq_disable();
+ get_paca()->hard_enabled = 0;
+
ctrl = mfspr(SPRN_CTRLF);
/* Enable DEC and EE interrupt request */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists