| 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
| ||
|
Message-ID: <511AC5A8.4030509@linaro.org> Date: Tue, 12 Feb 2013 23:43:52 +0100 From: Daniel Lezcano <daniel.lezcano@...aro.org> To: Len Brown <lenb@...nel.org> CC: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com> Subject: Re: [PATCH 14/16] intel_idle: remove use and definition of MWAIT_MAX_NUM_CSTATES On 02/12/2013 12:46 AM, Len Brown wrote: > On 02/11/2013 03:53 AM, Daniel Lezcano wrote: >> On 02/09/2013 02:08 AM, Len Brown wrote: > >>> The reason to change is that intel_idle will soon be able >>> to export more than the 8 "major" states supported by MWAIT. >>> When we hit that limit, it is important to know >>> where the limit comes from. >> >> Does it mean CPUIDLE_STATE_MAX may increase in a near future ? > > Yes, perhaps to 10. > Let me know if you anticipate issues with doing that. No, I don't see any issue so far. Maybe the array state is increasing more and more, so for most architecture it is a waste of memory, but anyway ... -- <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook | <http://twitter.com/#!/linaroorg> Twitter | <http://www.linaro.org/linaro-blog/> Blog -- 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