From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752578AbYIBMWd (ORCPT ); Tue, 2 Sep 2008 08:22:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751248AbYIBMWZ (ORCPT ); Tue, 2 Sep 2008 08:22:25 -0400 Received: from www.tglx.de ([62.245.132.106]:49543 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751223AbYIBMWZ (ORCPT ); Tue, 2 Sep 2008 08:22:25 -0400 Date: Tue, 2 Sep 2008 14:21:43 +0200 (CEST) From: Thomas Gleixner To: Andi Kleen cc: Linus Torvalds , Larry Finger , LKML , "Rafael J. Wysocki" , Alok Kataria , Michael Buesch Subject: Re: Regression in 2.6.27 caused by commit bfc0f59 In-Reply-To: <87k5dvvysd.fsf@basil.nowhere.org> Message-ID: References: <48BB2116.1060904@lwfinger.net> <48BC2A03.9000104@lwfinger.net> <87k5dvvysd.fsf@basil.nowhere.org> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2 Sep 2008, Andi Kleen wrote: > Thomas Gleixner writes: > > > > The whole ACPI code relies pretty much on PM_TIMER and as I said > > The Linux ACPI code does not rely on PM_TIMER in any special ways AFAIK > (except that it occasionally uses standard linux timer functions) > It merely discovers it for use by the other pmtimer users. # grep -rc acpi_gbl_FADT.xpm_timer_block.address drivers/acpi/ | grep -v ":0" drivers/acpi/processor_idle.c:12 I need to correct myself. It's only the processor_idle code :) Thanks, tglx