This patchset intends to add frequency throttle reporting mechanism
to powernv-cpufreq driver when OCC throttles the frequency. OCC is an
On-Chip-Controller which takes care of the power and thermal safety of
the chip. The CPU frequency can be throttled during an OCC reset or
when OCC tries to limit the max allowed frequency. The patchset will
report such conditions so as to keep the user informed about reason
for the drop in performance of workloads when frequency is throttled.
Changes from v3:
- Rebased on top of 4.2-rc1
- Minor changes in patch 2,3,4,6 this does not change the
functionality of the code
- 594fcb9ec9e powerpc/powernv: Expose OPAL APIs required by PRD
interface , this patch fixes the build error due to which this
series was initially dropped
ERROR: ".opal_message_notifier_register"
drivers/cpufreq/powernv-cpufreq.ko] undefined!
Changes from v2:
- Split into multiple patches
- Semantic fixes
Shilpasri G Bhat (6):
cpufreq: powernv: Handle throttling due to Pmax capping at chip level
powerpc/powernv: Add definition of OPAL_MSG_OCC message type
cpufreq: powernv: Register for OCC related opal_message notification
cpufreq: powernv: Call throttle_check() on receiving OCC_THROTTLE
cpufreq: powernv: Report Psafe only if PMSR.psafe_mode_active bit is
set
cpufreq: powernv: Restore cpu frequency to policy->cur on unthrottling
arch/powerpc/include/asm/opal-api.h | 12 +++
drivers/cpufreq/powernv-cpufreq.c | 195 +++++++++++++++++++++++++++++++++---
2 files changed, 192 insertions(+), 15 deletions(-)
--
1.9.3
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
