linux-kernel - Re: [PATCH 0/6] Intel pstate driver update

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4686510.A1KmKYg1tS@vostro.rjw.lan>
Date:	Wed, 08 May 2013 02:07:15 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	dirk.brandewie@...il.com
Cc:	linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org,
	Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 0/6] Intel pstate driver update

On Tuesday, May 07, 2013 08:20:24 AM dirk.brandewie@...il.com wrote:
> From: dirk <dirk.brandewie@...il.com>
> 
> Collection of updates for cpufreq/intel_pstate.c
> 
> Patches 1-3 are bugfixes and marked for stable
> 
> Patches 4-6 are code cleanup with no functional changes.
> 
> 
> Dirk Brandewie (6):
>   cpufreq/intel_pstate: remove idle time and duration from sample and
>     calculations
>   cpufreq/intel_pstate: use lowest requested max performance
>   cpufreq/intel_pstate: fix ffmpeg regression
>   cpufreq/intel_pstate: Remove idle mode PID
>   cpufreq/intel_pstate: Remove unused code
>   cpufreq/intel_pstate: remove #ifdef MODULE compile fence
> 
>  drivers/cpufreq/intel_pstate.c | 122 +++++++----------------------------------
>  1 file changed, 20 insertions(+), 102 deletions(-)

All queued up for a post-3.10-rc1 push as 3.10 material, but I have a couple
of comments.

First, the patches didn't apply for me cleanly.  I needed to fix up one of
them manually to make it apply and patch [5/6] didn't appear to be necessary
at all (it made changes that had been made previously).  Please check the
bleeding-edge branch of my tree to see if the code is what you wanted and
let me know (either way).

Second, can you please CC your cpufreq submissions to linux-pm@...r.kernel.org?
That will allow me to use Patchwork for managing them, which is much more
convenient than plain email.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/