From: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Cc: rjw@rjwysocki.net, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org, pc@us.ibm.com,
Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Subject: [PATCH v3 0/2] cpufreq: powernv: Redesign the presentation of throttle notification
Date: Mon, 4 Jan 2016 14:55:25 +0530 [thread overview]
Message-ID: <1451899527-14359-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> (raw)
In-Reply-To: <1451686914-3761-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com>
In POWER8, OCC(On-Chip-Controller) can throttle the frequency of the
CPU when the chip crosses its thermal and power limits. Currently,
powernv-cpufreq driver detects and reports this event as a console
message. Some boxes may not sustain the max turbo frequency in all
conditions and can be throttled frequently. This can lead to the
flooding of console with throttle messages. So this patchset aims to
redesign the presentation of this event via sysfs counters and
tracepoints.
This patchset will add a perf trace point "power:powernv_throttle" and
sysfs throttle counter stats in /sys/devices/system/cpu/cpufreq/chipN.
Changes from v2:
- Fixed kbuild test warning.
drivers/cpufreq/powernv-cpufreq.c:609:2: warning: ignoring return
value of 'kstrtoint', declared with attribute warn_unused_result
[-Wunused-result]
Shilpasri G Bhat (2):
cpufreq: powernv/tracing: Add powernv_throttle tracepoint
cpufreq: powernv: Redesign the presentation of throttle notification
drivers/cpufreq/powernv-cpufreq.c | 256 +++++++++++++++++++++++++++++++-------
include/trace/events/power.h | 22 ++++
kernel/trace/power-traces.c | 1 +
3 files changed, 236 insertions(+), 43 deletions(-)
--
1.9.3
next prev parent reply other threads:[~2016-01-04 9:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 22:21 [PATCH v2 0/2] cpufreq: powernv: Redesign the presentation of throttle notification Shilpasri G Bhat
2016-01-01 22:21 ` [PATCH v2 1/2] cpufreq: powernv/tracing: Add powernv_throttle tracepoint Shilpasri G Bhat
2016-01-01 22:21 ` [PATCH v2 2/2] cpufreq: powernv: Redesign the presentation of throttle notification Shilpasri G Bhat
2016-01-01 23:01 ` kbuild test robot
2016-01-02 2:08 ` kbuild test robot
2016-01-04 9:25 ` Shilpasri G Bhat [this message]
2016-01-04 9:25 ` [PATCH v3 1/2] cpufreq: powernv/tracing: Add powernv_throttle tracepoint Shilpasri G Bhat
2016-01-04 9:25 ` [PATCH v3 2/2] cpufreq: powernv: Redesign the presentation of throttle notification Shilpasri G Bhat
2016-01-06 6:51 ` [PATCH v3 0/2] " Stewart Smith
2016-01-11 20:54 ` [PATCH v4 0/4] " Shilpasri G Bhat
2016-01-11 20:54 ` [PATCH v4 1/4] cpufreq: powernv: Remove cpu_to_chip_id() from hot-path Shilpasri G Bhat
2016-01-11 20:54 ` [PATCH v4 2/4] cpufreq: powernv/tracing: Add powernv_throttle tracepoint Shilpasri G Bhat
2016-01-11 20:54 ` [PATCH v4 3/4] cpufreq: powernv: Add a trace print for the throttle event Shilpasri G Bhat
2016-01-11 20:54 ` [PATCH v4 4/4] cpufreq: powernv: Add sysfs attributes to show throttle stats Shilpasri G Bhat
2016-01-11 22:23 ` [PATCH v4 0/4] cpufreq: powernv: Redesign the presentation of throttle notification Greg KH
2016-01-12 2:32 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1451899527-14359-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com \
--to=shilpa.bhat@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pc@us.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).