From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 9BFF72C007C for ; Tue, 10 Jul 2012 17:49:47 +1000 (EST) Message-ID: <1341906580.2561.13.camel@pasglop> Subject: Re: [PATCH] More fixes for lazy IRQ vs. idle From: Benjamin Herrenschmidt To: Michael Neuling Date: Tue, 10 Jul 2012 17:49:40 +1000 In-Reply-To: <21083.1341900615@neuling.org> References: <1341891538.2561.10.camel@pasglop> <21083.1341900615@neuling.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2012-07-10 at 16:10 +1000, Michael Neuling wrote: > Benjamin Herrenschmidt wrote: > > > Looks like we still have issues with pSeries and Cell idle code > > vs. the lazy irq state. In fact, the reset fixes that went upstream > > are exposing the problem more by causing BUG_ON() to trigger (which > > this patch turns into a WARN_ON instead). > > Do we need to cc stable for 3.4 or is this new stuff only effecting us > since the 3.5 merge window? That's probably stable business, I'll check that before I send it to Linus. Cheers, Ben.