| 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: <6482671.TgGT1bSQ5Q@vostro.rjw.lan> Date: Wed, 29 Jul 2015 02:15:02 +0200 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Pan Xinhui <xinhuix.pan@...el.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>, Viresh Kumar <viresh.kumar@...aro.org>, "mnipxh@....com" <mnipxh@....com>, "yanmin_zhang@...ux.intel.com" <yanmin_zhang@...ux.intel.com> Subject: Re: [PATCH] cpufreq: Add scaling frequency range support On Tuesday, July 28, 2015 11:32:19 AM Pan Xinhui wrote: > From: Pan Xinhui <xinhuix.pan@...el.com> > > Userspace at most time do cpufreq tests very much inconveniently. > Currently they have to echo min and max cpu freq separately like below: > echo 480000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq > echo 2240000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq And why is this a problem? > Add scaling_freq_range cpufreq attr to support userspace's demand. > Therefore it's easier for testers to write readable scripts like below: > echo 480000-2240000 > > /sys/devices/system/cpu/cpu0/cpufreq/scaling_freq_range I'm not sure I agree with the statement that this is more readable. Not applied. Thanks, Rafael -- 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