lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 25 Sep 2009 12:36:23 +0530 From: Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com> To: Arjan van de Ven <arjan@...radead.org> Cc: arun@...ux.vnet.ibm.com, Len Brown <lenb@...nel.org>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, Joel Schopp <jschopp@...tin.ibm.com>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>, Dipankar Sarma <dipankar@...ibm.com>, Balbir Singh <balbir@...ibm.com>, Gautham R Shenoy <ego@...ibm.com>, Shaohua Li <shaohua.li@...el.com>, Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>, linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, linux-acpi@...r.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. * Arjan van de Ven <arjan@...radead.org> [2009-09-24 14:22:28]: > On Thu, 24 Sep 2009 10:42:41 +0530 > Arun R Bharadwaj <arun@...ux.vnet.ibm.com> wrote: > > > * Arun R Bharadwaj <arun@...ux.vnet.ibm.com> [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@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists