linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle()
Date: Wed, 25 Nov 2015 10:57:44 -0800	[thread overview]
Message-ID: <20151125185743.GP2517@atomide.com> (raw)
In-Reply-To: <1447668561-6587-1-git-send-email-jszhang@marvell.com>

* Jisheng Zhang <jszhang@marvell.com> [151116 02:13]:
> The cpuidle tracepoints are called within a rcu_idle_exit() section, and
> must be denoted with the _rcuidle() version of the tracepoint.
> 
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> Acked-by: Kevin Hilman <khilman@linaro.org>

Sorry I have this in my omap-for-v4.4/fixes but have not sent out pull
request yet. Hoping to send it today or on Friday.

Regards,

Tony

> ---
>  arch/arm/mach-omap2/pm34xx.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 87b98bf9..2dbd378 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -301,11 +301,11 @@ static void omap3_pm_idle(void)
>  	if (omap_irq_pending())
>  		return;
>  
> -	trace_cpu_idle(1, smp_processor_id());
> +	trace_cpu_idle_rcuidle(1, smp_processor_id());
>  
>  	omap_sram_idle();
>  
> -	trace_cpu_idle(PWR_EVENT_EXIT, smp_processor_id());
> +	trace_cpu_idle_rcuidle(PWR_EVENT_EXIT, smp_processor_id());
>  }
>  
>  #ifdef CONFIG_SUSPEND
> -- 
> 2.6.2
> 

      reply	other threads:[~2015-11-25 18:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16 10:09 [PATCH RESEND] ARM: OMAP2+: PM: Denote the cpuidle tracepoints as _rcuidle() Jisheng Zhang
2015-11-25 18:57 ` Tony Lindgren [this message]

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=20151125185743.GP2517@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).