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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 26 Mar 2019 12:12:35 +0100
From:   "Rafael J. Wysocki" <>
To:     Linux PM <>
Cc:     LKML <>,
        Viresh Kumar <>,
        Srinivas Pandruvada <>,
        Chen Yu <>,
        Gabriele Mazzotta <>,
        Peter Zijlstra <>,
        Quentin Perret <>
Subject: [PATCH v3 0/4] cpufreq: intel_pstate: Handle _PPC updates on global turbo disable/enable

Hi All,

This is a new version of the following with one patch added:

> This is a follow-up to the RFT patch set posted previously:
> Patch [1/3] causes intel_pstate to update all policies if it gets a _PPC
> change notification and sees a global turbo disable/enable change.
> Patch [2/3] adds cpufreq_cpu_acquire() and cpufreq_cpu_release() to reduce
> code duplication after the next patch a bit (and Srinivas wanted the rwsem
> manipulation to not be done directly by the driver).
> Patch [3/3] makes intel_pstate update cpuinfo.max_freq for all policies in
> those cases.
> I've atted Tested-by tags to patches [1/3] and [3/3], because there are only
> cosmetic differences between them and what has been tested..

The new patch goes (as the new [3/4]) before the old [3/3] (which becomes the
new [4/4] obviously) and it modifies the schedutil governor to prevent it
from caching values that depend on cpuinfo.max_freq.

The other patches are the same as before.


Powered by blists - more mailing lists