From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, tglx@linutronix.de, rjw@rjwysocki.net,
nicolas.pitre@linaro.org, preeti@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 4/5] idle: Move idle conditions in cpuidle_idle main function
Date: Mon, 24 Feb 2014 16:39:08 +0100 [thread overview]
Message-ID: <530B679C.6070204@linaro.org> (raw)
In-Reply-To: <20140224145912.GW27965@twins.programming.kicks-ass.net>
On 02/24/2014 03:59 PM, Peter Zijlstra wrote:
> On Mon, Feb 24, 2014 at 02:55:50PM +0100, Daniel Lezcano wrote:
>> @@ -136,25 +155,8 @@ static void cpu_idle_loop(void)
>> local_irq_disable();
>> arch_cpu_idle_enter();
>>
>> - /*
>> - * In poll mode we reenable interrupts and spin.
>> - *
>> - * Also if we detected in the wakeup from idle
>> - * path that the tick broadcast device expired
>> - * for us, we don't want to go deep idle as we
>> - * know that the IPI is going to arrive right
>> - * away
>> - */
>> - if (cpu_idle_force_poll || tick_check_broadcast_expired()) {
>> - cpu_idle_poll();
>> - } else {
>> - if (!current_clr_polling_and_test()) {
>> - cpuidle_idle_call();
>> - } else {
>> - local_irq_enable();
>> - }
>> - __current_set_polling();
>> - }
>> + cpuidle_idle_call();
>> +
>
> Yeah, not liking that much; you can make it look like:
>
> if (cpu_idle_force_poll || tick_check_broadcast_expired())
> cpu_idle_poll();
> else
> cpu_idle_call();
>
> Though. That keeps the polling case separate from the actual idle
> function.
Yes, you are right, it looks better.
> And when you do that; you can also push down the
> current_clr_polling_and_test() muck so it doesn't cover the actual
> cpuidle policy code.
I am not getting it. Where do you suggest to move it ?
--
<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-02-24 15:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 13:55 [PATCH V2 1/5] idle/cpuidle: Split cpuidle_idle_call main function into smaller functions Daniel Lezcano
2014-02-24 13:55 ` [PATCH V2 2/5] cpuidle/idle: Move the cpuidle_idle_call function to idle.c Daniel Lezcano
2014-02-24 13:55 ` [PATCH V2 3/5] idle: Reorganize the idle loop Daniel Lezcano
2014-02-24 13:55 ` [PATCH V2 4/5] idle: Move idle conditions in cpuidle_idle main function Daniel Lezcano
2014-02-24 14:59 ` Peter Zijlstra
2014-02-24 15:39 ` Daniel Lezcano [this message]
2014-02-24 16:05 ` Peter Zijlstra
2014-02-24 17:03 ` Daniel Lezcano
2014-02-24 17:22 ` Peter Zijlstra
2014-02-24 17:54 ` Nicolas Pitre
2014-02-24 17:58 ` Peter Zijlstra
2014-02-24 19:04 ` Daniel Lezcano
2014-02-24 19:25 ` Peter Zijlstra
2014-02-27 13:32 ` [tip:sched/core] sched/idle: Remove stale old file tip-bot for Peter Zijlstra
2014-02-24 13:55 ` [PATCH V2 5/5] idle: Add more comments to the code Daniel Lezcano
2014-02-24 15:00 ` [PATCH V2 1/5] idle/cpuidle: Split cpuidle_idle_call main function into smaller functions Peter Zijlstra
2014-02-24 15:12 ` Daniel Lezcano
2014-02-24 15:16 ` Peter Zijlstra
2014-02-25 3:35 ` Preeti U Murthy
2014-02-25 3:47 ` Preeti U Murthy
2014-02-25 6:35 ` 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=530B679C.6070204@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.