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: Wed, 15 Nov 2017 16:55:32 +0530 From: Viresh Kumar <viresh.kumar@...aro.org> To: Daniel Lezcano <daniel.lezcano@...aro.org> Cc: Rafael Wysocki <rjw@...ysocki.net>, edubezval@...il.com, Amit Daniel Kachhap <amit.kachhap@...il.com>, Javi Merino <javi.merino@...nel.org>, Zhang Rui <rui.zhang@...el.com>, Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...hat.com>, linux-pm@...r.kernel.org, Vincent Guittot <vincent.guittot@...aro.org>, lukasz.luba@....com, linux-kernel@...r.kernel.org, Javi Merino <javi.merino@....com>, Punit Agrawal <punit.agrawal@....com> Subject: Re: [PATCH 4/4] cpu_cooling: Drop static-power related stuff On 15-11-17, 11:18, Daniel Lezcano wrote: > Even if I agree that is not used to in the mainstream kernel, it is part > of the EAS which is currently merged in Android. Okay, I had chat with Daniel offline after looking at Android sources and here are the key-points: - No one is using this feature currently in Mainline or Android kernel tree. - There may be some SoC vendors who are using it on their local repos, but we don't have much details on that. - For EAS (Energy aware scheduling), we want to take static power of the CPUs into account and that is a TODO thing right now. What worries me is that this code got merged almost 2.5 years back and no one used it. Yeah, it looks interesting stuff but what's the guarantee that anyone is going to use it in near future ? @Javi, @Puneet, @Lukasz: As it was added by Javi (from ARM), can someone from ARM write a patch for the arm big LITTLE cpufreq driver (Juno?) and use this thing? Else I am not sure how long we want to keep code in kernel that no one touches. And of course, we can revert this commit later on if required without much trouble hopefully. -- viresh
Powered by blists - more mailing lists