linux-kernel - Fwd: [PATCH] cpufreq: allow powersave governor as the default without expert mode

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 16 Oct 2014 08:44:45 -0400
From:	James Geboski <jgeboski@...il.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Fwd: [PATCH] cpufreq: allow powersave governor as the default without
 expert mode

On Thu, Oct 16, 2014 at 6:27 AM, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> On 16 October 2014 15:50, James Geboski <jgeboski@...il.com> wrote:
>> The intel_pstate driver only supports the performance and the powersave
>> governors. With the performance governor ensuring the highest possible
>> performance settings, userspace tools fail to make any lasting changes.
>> In order to allow userspace tools to make modifications to the settings,
>> the powersave governor must be in use. This makes having the powersave
>> governor as the default convenient for systems where the intel_pstate
>> driver is being employed. Having to enable expert mode in the kernel
>> configuration is just a headache for such a trivial task.
>>
>> This patch applies to all kernel versions 2.6.38 or greater after the
>> migration from CONFIG_EMBEDDED to CONFIG_EXPERT (6a108a14fa35). Most
>> importantly, this applies to kernel versions 3.9 or greater when the
>> intel_pstate driver was introduced.
>>
>> Signed-off-by: James Geboski <jgeboski@...il.com>
>> Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
>> ---
>>  drivers/cpufreq/Kconfig | 1 -
>>  1 file changed, 1 deletion(-)
>
> Why did you resent it? Without any information at all about what has changed?

I added your Acked-by line to the patch message. However, I am apparently
incompetent with git-send-email. I have replied to the original thread,
please discard this thread. My apologizes for the excessive noise.
--
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/