Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424648AbWKPV0y (ORCPT ); Thu, 16 Nov 2006 16:26:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1424646AbWKPV0y (ORCPT ); Thu, 16 Nov 2006 16:26:54 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:63909 "HELO iolanthe.rowland.org") by vger.kernel.org with SMTP id S1424636AbWKPV0x (ORCPT ); Thu, 16 Nov 2006 16:26:53 -0500 Date: Thu, 16 Nov 2006 16:26:52 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Thomas Gleixner cc: LKML , Linus Torvalds , john stultz , Ingo Molnar , David Miller , Arjan van de Ven , Andrew Morton , Andi Kleen Subject: Re: BUG: cpufreq notification broken In-Reply-To: <1163711368.10333.41.camel@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 739 Lines: 19 On Thu, 16 Nov 2006, Thomas Gleixner wrote: > There is another issue with this SRCU change: > > The notification comes actually after the real change, which is bad. We > try to make the TSC usable by backing it with pm_timer accross such > states, but this behaviour breaks the safety code. I don't understand. Sending notifications is completely separate from setting up the notifier chain's head. The patch you mentioned didn't touch the code that sends the notifications. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/