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, 28 May 2010 10:07:34 +0200 From: Thomas Renninger <trenn@...e.de> To: Len Brown <lenb@...nel.org> Cc: linux-pm@...ts.linux-foundation.org, x86@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] idle-test patches queued for upstream On Friday 28 May 2010 02:59:07 Len Brown wrote: > > > ... we think we can do better than ACPI. > > > Why exactly? Is there any info missing in the ACPI tables? > > Or is this just to be more independent from OEMs? > > ACPI has a few fundmental flaws here. One is that it reports > exit latency instead of break-even power duration. > The other is that it requires a BIOS writer to > get the tables right. This is a general ACPI problem... > > Using ACPI table based C-states by default and using > > intel_idle.enable=1 > > or similar for workarounds sounds safer. > > At least as long as the driver is experimental. > > I plan to remove the EXPERIMENTAL in 1 release. > > > Does Windows use ACPI C-state info for idle? > Yes, Windows uses ACPI. > On the Dell above, that is why Linux consumes 15% less idle power > and why Linux can take advantage of turbo mode and Windows can not. You always propageted to stay Windows compatible... Now we go the untested way. Let's see how much machines will break... Thanks for clarifications, Thomas -- 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