cpufreq: intel_pstate: Handle _PPC updates on global turbo disable/enable
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest4 patches 5 repliesIn review
- v23 patches 3 repliesSuperseded
- v12 patches 31 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | cpufreq: intel_pstate: Driver-specific handling of _PPC updatesdrivers/ drivers/ drivers/ +1 more | +45 | 0 replies | |
| 2/4 | cpufreq: Add cpufreq_cpu_acquire() and cpufreq_cpu_release()drivers/ | +47 | 0 replies | |
| 3/4 | cpufreq: schedutil: Simplify iowait boostingkernel/ | +5 | 2 replies | |
| 3/4 | cpufreq: schedutil: Simplify iowait boostingkernel/ | +10 | 3 replies | |
| 4/4 | cpufreq: intel_pstate: Update max frequency on global turbo changesdrivers/ drivers/ include/ | +43 | 0 replies |
Reviews trailers per patch
All 5 patches have a Reviewed-by or Acked-by.
| Patch | Gabriele Mazzotta | Viresh Kumar | Peter Zijlstra (Intel) |
|---|---|---|---|
| 1/4 | T-b | A-b | |
| 2/4 | A-b | ||
| 3/4 | A-b | A-b | |
| 3/4 | A-b | A-b | |
| 4/4 | T-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [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:
Quoted 10 lines
This is a follow-up to the RFT patch set posted previously:
https://lore.kernel.org/lkml/[email protected]/Patch [1/3] causes
intel_pstateto update all policies if it gets a_PPCchange notification and sees a global turbo disable/enable change.Patch [2/3] adds
cpufreq_cpu_acquire()andcpufreq_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).
Quoted 5 lines
Patch [3/3] makes
intel_pstateupdate 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.
Thanks,
Rafael