Linux Power Management development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Dong Aisheng <aisheng.dong@nxp.com>,
	Fabio Estevam <festevam@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Anson Huang <anson.huang@nxp.com>,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: imx6q: Fixup RCU usage for cpuidle
Date: Wed, 30 Sep 2020 13:33:25 +0200	[thread overview]
Message-ID: <20200930113325.GA2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200930112023.121821-1-ulf.hansson@linaro.org>

On Wed, Sep 30, 2020 at 01:20:23PM +0200, Ulf Hansson wrote:
> The commit eb1f00237aca ("lockdep,trace: Expose tracepoints"), started to
> expose us for tracepoints. For imx6q cpuidle, this leads to an RCU splat
> according to below.
> 
> [6.870684] [<c0db7690>] (_raw_spin_lock) from [<c011f6a4>] (imx6q_enter_wait+0x18/0x9c)
> [6.878846] [<c011f6a4>] (imx6q_enter_wait) from [<c09abfb0>] (cpuidle_enter_state+0x168/0x5e4)
> 
> To fix the problem, let's assign the corresponding idlestate->flags the
> CPUIDLE_FLAG_RCU_IDLE bit, which enables us to call rcu_idle_enter|exit()
> at the proper point.
> 
> Reported-by: Dong Aisheng <aisheng.dong@nxp.com>
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

Yep, that looks about right.

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

> ---
>  arch/arm/mach-imx/cpuidle-imx6q.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/mach-imx/cpuidle-imx6q.c b/arch/arm/mach-imx/cpuidle-imx6q.c
> index 24dd5bbe60e4..094337dc1bc7 100644
> --- a/arch/arm/mach-imx/cpuidle-imx6q.c
> +++ b/arch/arm/mach-imx/cpuidle-imx6q.c
> @@ -24,7 +24,9 @@ static int imx6q_enter_wait(struct cpuidle_device *dev,
>  		imx6_set_lpm(WAIT_UNCLOCKED);
>  	raw_spin_unlock(&cpuidle_lock);
>  
> +	rcu_idle_enter();
>  	cpu_do_idle();
> +	rcu_idle_exit();
>  
>  	raw_spin_lock(&cpuidle_lock);
>  	if (num_idle_cpus-- == num_online_cpus())
> @@ -44,7 +46,7 @@ static struct cpuidle_driver imx6q_cpuidle_driver = {
>  		{
>  			.exit_latency = 50,
>  			.target_residency = 75,
> -			.flags = CPUIDLE_FLAG_TIMER_STOP,
> +			.flags = CPUIDLE_FLAG_TIMER_STOP | CPUIDLE_FLAG_RCU_IDLE,
>  			.enter = imx6q_enter_wait,
>  			.name = "WAIT",
>  			.desc = "Clock off",
> -- 
> 2.25.1
> 

  reply	other threads:[~2020-09-30 11:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 11:20 [PATCH] ARM: imx6q: Fixup RCU usage for cpuidle Ulf Hansson
2020-09-30 11:33 ` Peter Zijlstra [this message]
2020-09-30 15:44   ` 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=20200930113325.GA2628@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=aisheng.dong@nxp.com \
    --cc=anson.huang@nxp.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=ulf.hansson@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