On 4 May 2015 at 14:24, Shilpasri G Bhat <[email protected]> wrote: > 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 v2: > - Split into multiple patches > - Semantic fixes > > Shilpasri G Bhat (6): > cpufreq: poowernv: 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 | 8 ++ > drivers/cpufreq/powernv-cpufreq.c | 199 > +++++++++++++++++++++++++++++++++--- > 2 files changed, 192 insertions(+), 15 deletions(-)
Acked-by: Viresh Kumar <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
