Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752406AbZIYHGs (ORCPT ); Fri, 25 Sep 2009 03:06:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752007AbZIYHGp (ORCPT ); Fri, 25 Sep 2009 03:06:45 -0400 Received: from e23smtp04.au.ibm.com ([202.81.31.146]:39211 "EHLO e23smtp04.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751880AbZIYHGo (ORCPT ); Fri, 25 Sep 2009 03:06:44 -0400 Date: Fri, 25 Sep 2009 12:36:23 +0530 From: Vaidyanathan Srinivasan To: Arjan van de Ven Cc: arun@linux.vnet.ibm.com, Len Brown , Peter Zijlstra , Joel Schopp , Benjamin Herrenschmidt , Paul Mackerras , Ingo Molnar , Dipankar Sarma , Balbir Singh , Gautham R Shenoy , Shaohua Li , Venkatesh Pallipadi , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-acpi@vger.kernel.org Subject: Re: [v6 PATCH 0/7]: cpuidle/x86/POWER: Cleanup idle power management code in x86, cleanup drivers/cpuidle/cpuidle.c and introduce cpuidle to POWER. Message-ID: <20090925070623.GH8595@dirshya.in.ibm.com> Reply-To: svaidy@linux.vnet.ibm.com References: <20090922112526.GA7788@linux.vnet.ibm.com> <20090924051238.GA5963@linux.vnet.ibm.com> <20090924142228.5a2ddf59@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20090924142228.5a2ddf59@infradead.org> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1263 Lines: 37 * Arjan van de Ven [2009-09-24 14:22:28]: > On Thu, 24 Sep 2009 10:42:41 +0530 > Arun R Bharadwaj wrote: > > > * Arun R Bharadwaj [2009-09-22 16:55:27]: > > > > Hi Len, (or other acpi folks), > > > > I had a question regarding ACPI-cpuidle interaction in the current > > implementation. > > > > Currently, every cpu (i.e. acpi_processor) registers to cpuidle as > > a cpuidle_device. So every cpu has to go through the process of > > setting up the idle states and then registering as a cpuidle device. > > > > What exactly is the reason behind this? > > > > technically a BIOS can opt to give you C states via ACPI on some cpus, > but not on others. > > in practice when this happens it tends to be a bug.. but it's > technically a valid configuration So we will need to keep the per-cpu registration as of now because we may have such buggy BIOS in the field and we don't want the cpuidle framework to malfunction there. --Vaidy -- 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/