From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Colin Cross <ccross@android.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] cpuidle: coupled: Enable interrupts when early returning on invalid driver
Date: Thu, 24 Jul 2014 11:35:04 +0200 [thread overview]
Message-ID: <53D0D348.406@linaro.org> (raw)
In-Reply-To: <1406193999-20300-1-git-send-email-k.kozlowski@samsung.com>
On 07/24/2014 11:26 AM, Krzysztof Kozlowski wrote:
> cpuidle_enter_state is expected to return with interrupts enabled.
> However cpuidle_enter_state_coupled returned with interrupts disabled if
> the cpuidle driver was registered without mask of coupled cpus.
Hi Krzysztof,
may be your patch is right but I would like to clarify one thing. This
is the cpuidle driver for exynos. AFAICT, the coupled states shouldn't
be enabled for this driver, so how did you face this issue ?
> This could be observed as a warning:
> [ 1.613132] ------------[ cut here ]------------
> [ 1.613244] WARNING: CPU: 0 PID: 0 at kernel/sched/idle.c:175 cpu_idle_loop+0x2dc/0x6d0()
> [ 1.620268] Modules linked in:
> [ 1.623311] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-rc4-00102-g7669ccdbf8af-dirty #81
> [ 1.623619] dwmmc_exynos 12510000.mshc: 1 slots initialized
> [ 1.624890] logger: created 256K log 'log_main'
> [ 1.625483] logger: created 256K log 'log_events'
> [ 1.626084] logger: created 256K log 'log_radio'
> [ 1.626699] logger: created 256K log 'log_system'
> [ 1.655960] [<c00167cc>] (unwind_backtrace) from [<c0012c28>] (show_stack+0x10/0x14)
> [ 1.663679] [<c0012c28>] (show_stack) from [<c050ab00>] (dump_stack+0x70/0xbc)
> [ 1.670883] [<c050ab00>] (dump_stack) from [<c0023ac8>] (warn_slowpath_common+0x68/0x8c)
> [ 1.678954] [<c0023ac8>] (warn_slowpath_common) from [<c0023b08>] (warn_slowpath_null+0x1c/0x24)
> [ 1.687720] [<c0023b08>] (warn_slowpath_null) from [<c006ddd4>] (cpu_idle_loop+0x2dc/0x6d0)
> [ 1.696052] [<c006ddd4>] (cpu_idle_loop) from [<c006e1d4>] (cpupri_find+0x0/0xd4)
> [ 1.703518] [<c006e1d4>] (cpupri_find) from [<c07cdd14>] (processor_id+0x0/0x2c)
> [ 1.710917] ---[ end trace a85327313857296e ]---
>
> Enable the interrupts also when early returning from
> cpuidle_enter_state_coupled due to invalid coupled configuration.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Fixes: 4126c0197bc8 ("cpuidle: add support for states that affect multiple cpus")
> Cc: <stable@vger.kernel.org>
> ---
> drivers/cpuidle/coupled.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c
> index 73fe2f8d7f96..2b57c267e855 100644
> --- a/drivers/cpuidle/coupled.c
> +++ b/drivers/cpuidle/coupled.c
> @@ -463,8 +463,10 @@ int cpuidle_enter_state_coupled(struct cpuidle_device *dev,
> struct cpuidle_coupled *coupled = dev->coupled;
> int w;
>
> - if (!coupled)
> + if (!coupled) {
> + local_irq_enable();
> return -EINVAL;
> + }
>
> while (coupled->prevent) {
> cpuidle_coupled_clear_pokes(dev->cpu);
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2014-07-24 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 9:26 [PATCH] cpuidle: coupled: Enable interrupts when early returning on invalid driver Krzysztof Kozlowski
2014-07-24 9:35 ` Daniel Lezcano [this message]
2014-07-24 9:46 ` Krzysztof Kozlowski
2014-07-24 10:27 ` Daniel Lezcano
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=53D0D348.406@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=ccross@android.com \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=stable@vger.kernel.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).