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 DE3EADDDB5 for ; Thu, 12 Feb 2009 17:05:55 +1100 (EST) Subject: Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) From: Benjamin Herrenschmidt To: Thomas Gleixner In-Reply-To: References: <87prihcepl.fsf@burly.wgtn.ondioline.org> <87k58nda87.fsf@burly.wgtn.ondioline.org> <874oz5pmvd.fsf@burly.wgtn.ondioline.org> <200902081439.31548.rjw@sisk.pl> Content-Type: text/plain Date: Thu, 12 Feb 2009 17:05:24 +1100 Message-Id: <1234418724.29851.53.camel@pasglop> Mime-Version: 1.0 Cc: "Rafael J. Wysocki" , linuxppc-dev@ozlabs.org, Ingo Molnar , Paul Collins , linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > The commit fixed the problem with sched_clock, but it does not fix > problems where other parts of the kernel call timekeeping functions > _AFTER_ timekeeping has been suspended. Maybe we should use the PMU sysdev which is used for suspending backlight stuff etc... to also suspend emitting of the input events. Cheers, Ben.