mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [Resend][PATCH] PM / tick: Add tracepoints for suspend-to-idle diagnostics
Date: Fri, 15 May 2015 00:04:57 +0200	[thread overview]
Message-ID: <9746445.jijJSAGWOf@vostro.rjw.lan> (raw)
In-Reply-To: <1543314.9EN5CRZp0f@vostro.rjw.lan>

On Sunday, May 10, 2015 01:23:35 AM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Add suspend/resume tracepoints to tick_freeze() and tick_unfreeze()
> to catch when timekeeping is suspended and resumed during suspend-to-idle
> so as to be able to check whether or not we enter the "frozen" state
> and to measure the time spent in it.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Thomas, Peter, any objections here?

> ---
> 
> Sorry for the duplication, but I messed up the Thomas' address in the previous one.
> 
> ---
>  kernel/time/tick-common.c |   15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)
> 
> Index: linux-pm/kernel/time/tick-common.c
> ===================================================================
> --- linux-pm.orig/kernel/time/tick-common.c
> +++ linux-pm/kernel/time/tick-common.c
> @@ -19,6 +19,7 @@
>  #include <linux/profile.h>
>  #include <linux/sched.h>
>  #include <linux/module.h>
> +#include <trace/events/power.h>
>  
>  #include <asm/irq_regs.h>
>  
> @@ -457,10 +458,13 @@ void tick_freeze(void)
>  	raw_spin_lock(&tick_freeze_lock);
>  
>  	tick_freeze_depth++;
> -	if (tick_freeze_depth == num_online_cpus())
> +	if (tick_freeze_depth == num_online_cpus()) {
> +		trace_suspend_resume(TPS("timekeeping_freeze"),
> +				     smp_processor_id(), true);
>  		timekeeping_suspend();
> -	else
> +	} else {
>  		tick_suspend_local();
> +	}
>  
>  	raw_spin_unlock(&tick_freeze_lock);
>  }
> @@ -478,10 +482,13 @@ void tick_unfreeze(void)
>  {
>  	raw_spin_lock(&tick_freeze_lock);
>  
> -	if (tick_freeze_depth == num_online_cpus())
> +	if (tick_freeze_depth == num_online_cpus()) {
>  		timekeeping_resume();
> -	else
> +		trace_suspend_resume(TPS("timekeeping_freeze"),
> +				     smp_processor_id(), false);
> +	} else {
>  		tick_resume_local();
> +	}
>  
>  	tick_freeze_depth--;
>  
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2015-05-14 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 23:09 [PATCH] " Rafael J. Wysocki
2015-05-09 23:23 ` [Resend][PATCH] " Rafael J. Wysocki
2015-05-14 22:04   ` Rafael J. Wysocki [this message]
2015-05-14 21:43     ` Thomas Gleixner
2015-05-14 23:42       ` Rafael J. Wysocki

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=9746445.jijJSAGWOf@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®