public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	javi.merino@arm.com, rui.zhang@intel.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/3] Add trace to thermal framework
Date: Tue, 29 Jul 2014 09:33:27 -0400	[thread overview]
Message-ID: <20140729133327.GA3336@developer> (raw)
In-Reply-To: <1406631050-14975-1-git-send-email-punit.agrawal@arm.com>

On Tue, Jul 29, 2014 at 11:50:47AM +0100, Punit Agrawal wrote:
> Hi linux-pm,
> 
> This is the second posting of the patches to add trace to the thermal
> framework.
> 
> The linux thermal framework doesn't have any support for tracing. This
> makes it hard to run workloads and observe the thermal behaviour of
> the system without actively polling files in sysfs or enabling debug
> builds.
> 
> This patch set introduces trace events in the framework to allow
> observing the behaviour of the different components in the
> framework. The events added trace temperature changes, trip points and
> cooling device state changes.
> 
> changes since rfc:
> * Fixed an issue where incorrect trip point was traced when using fair
> share
> * Trace the numeric value of trip_type instead of using __print_symbolic

Pulled the series.

Thanks.

> 
> Punit Agrawal (3):
>   thermal: trace: Trace temperature changes
>   thermal: trace: Trace when a cooling device's state is updated
>   thermal: trace: Trace when temperature is above a trip point
> 
>  drivers/thermal/fair_share.c   |   12 ++++++
>  drivers/thermal/step_wise.c    |    5 ++-
>  drivers/thermal/thermal_core.c |    7 ++++
>  include/trace/events/thermal.h |   87 ++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 110 insertions(+), 1 deletion(-)
>  create mode 100644 include/trace/events/thermal.h
> 
> -- 
> 1.7.10.4
> 

  parent reply	other threads:[~2014-07-29 13:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 11:31 [RFC PATCH 0/3] Add trace to thermal framework Punit Agrawal
2014-06-11 11:31 ` [RFC PATCH 1/3] thermal: trace: Trace temperature changes Punit Agrawal
2014-06-11 11:31 ` [RFC PATCH 2/3] thermal: trace: Trace when a cooling device's state is updated Punit Agrawal
2014-06-11 11:31 ` [RFC PATCH 3/3] thermal: trace: Trace when temperature is above a trip point Punit Agrawal
2014-06-11 12:49   ` Steven Rostedt
2014-06-11 14:11     ` Punit Agrawal
2014-06-11 14:20       ` Steven Rostedt
2014-06-11 14:53         ` Punit Agrawal
2014-06-11 15:08           ` Steven Rostedt
2014-06-12 16:16             ` Punit Agrawal
2014-06-20 17:24   ` Javi Merino
2014-06-24 10:41     ` Punit Agrawal
2014-06-25 13:26       ` Javi Merino
2014-07-25 14:11       ` edubezval
2014-07-29 10:50 ` [PATCH 0/3] Add trace to thermal framework Punit Agrawal
2014-07-29 10:50   ` [PATCH 1/3] thermal: trace: Trace temperature changes Punit Agrawal
2014-07-29 10:50   ` [PATCH 2/3] thermal: trace: Trace when a cooling device's state is updated Punit Agrawal
2014-07-29 10:50   ` [PATCH 3/3] thermal: trace: Trace when temperature is above a trip point Punit Agrawal
2014-07-29 13:33   ` Eduardo Valentin [this message]
2014-07-30 11:40     ` [PATCH 0/3] Add trace to thermal framework Punit Agrawal

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=20140729133327.GA3336@developer \
    --to=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --cc=rostedt@goodmis.org \
    --cc=rui.zhang@intel.com \
    /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