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: Thu, 27 May 2010 07:14:46 -0700 From: Kevin Hilman <khilman@...prootsystems.com> To: Len Brown <lenb@...nel.org> Cc: x86@...nel.org, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com> Subject: Re: [PATCH 8/8] intel_idle: create a native cpuidle driver for select intel processors Len Brown <lenb@...nel.org> writes: > From: Len Brown <len.brown@...el.com> > > This EXPERIMENTAL driver supersedes acpi_idle > on modern Intel processors. (Nehalem and Atom Processors). > > For CONFIG_INTEL_IDLE=y, intel_idle probes before acpi_idle, > no matter if CONFIG_ACPI_PROCESSOR=y or =m. > > Boot with "intel_idle.max_cstate=0" to disable the driver > and to fall back on ACPI. > > CONFIG_INTEL_IDLE=m is not recommended unless the system > has a method to guarantee intel_idle loads before ACPI's > processor_idle. > > This driver does not yet know about cpu online/offline > and thus will not yet play well with cpu-hotplug. > > Signed-off-by: Len Brown <len.brown@...el.com> > --- > MAINTAINERS | 7 + > drivers/Makefile | 2 +- > drivers/acpi/processor_driver.c | 6 +- > drivers/idle/Kconfig | 11 + > drivers/idle/Makefile | 1 + > drivers/idle/intel_idle.c | 446 +++++++++++++++++++++++++++++++++++++++ Any reason this arch-specific driver needs to be in drivers/idle instead of under a platform specific dir like arch/x86? On embedded SoCs that have never had ACPI, we have our platform-specific CPUidle drivers in with the rest of our platform specific code. Kevin -- 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