From: Greg KH <gregkh@linuxfoundation.org>
To: Shilpasri G Bhat <shilpa.bhat@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
rjw@rjwysocki.net, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org, pc@us.ibm.com, anton@samba.org,
ego@linux.vnet.ibm.com, stable@vger.kernel.org
Subject: Re: [PATCH v4 0/4] cpufreq: powernv: Redesign the presentation of throttle notification
Date: Mon, 11 Jan 2016 14:23:12 -0800 [thread overview]
Message-ID: <20160111222312.GA3967@kroah.com> (raw)
In-Reply-To: <1452545680-11976-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com>
On Mon, Jan 11, 2016 at 02:54:36PM -0600, Shilpasri G Bhat wrote:
> 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 machines 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.
>
> Patches [2] to [4] will add a perf trace point "power:powernv_throttle" and
> sysfs throttle counter stats in /sys/devices/system/cpu/cpufreq/chipN.
> Patch [1] solves a bug in powernv_cpufreq_throttle_check(), which calls in to
> cpu_to_chip_id() in hot path which reads DT every time to find the chip id.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2016-01-11 22:23 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 ` [PATCH v3 0/2] " Shilpasri G Bhat
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 ` Greg KH [this message]
2016-01-12 2:32 ` [PATCH v4 0/4] cpufreq: powernv: Redesign the presentation of throttle notification 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=20160111222312.GA3967@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anton@samba.org \
--cc=ego@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=shilpa.bhat@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--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).