From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de,
rjw@rjwysocki.net
Cc: nicolas.pitre@linaro.org, preeti@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 5/5] idle: Add more comments to the code
Date: Tue, 11 Feb 2014 16:11:31 +0100 [thread overview]
Message-ID: <1392131491-5265-5-git-send-email-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <1392131491-5265-1-git-send-email-daniel.lezcano@linaro.org>
The idle main function is a complex and a critical function. Added more
comments to the code.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
kernel/sched/idle.c | 37 +++++++++++++++++++++++++++++++++----
1 file changed, 33 insertions(+), 4 deletions(-)
diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
index 72b5926..36ff1a7 100644
--- a/kernel/sched/idle.c
+++ b/kernel/sched/idle.c
@@ -86,19 +86,34 @@ static int cpuidle_idle_call(void)
if (cpu_idle_force_poll || tick_check_broadcast_expired())
return cpu_idle_poll();
+ /*
+ * Check if the idle task must rescheduled. If it is the case,
+ * exit the function after re-enabling the local irq and set
+ * again the polling flag
+ */
if (current_clr_polling_and_test()) {
local_irq_enable();
__current_set_polling();
return 0;
}
+ /*
+ * During the idle period, stop measuring the disabled irqs
+ * critical sections latencies
+ */
stop_critical_timings();
+
+ /*
+ * Tell the RCU framework we are entering an idle section,
+ * so no more rcu read side critical sections and one more
+ * step to the grace period
+ */
rcu_idle_enter();
- /* Ask the governor for the next state, this call can fail for
- * different reasons: cpuidle is not enabled or an idle state
- * fulfilling the constraints was not found. In this case, we fall
- * back to the default idle function
+ /*
+ * Ask the governor to choose an idle state it thinks it is
+ * convenient to go to. There is *always* a convenient idle
+ * state but the call could fail if cpuidle is not enabled
*/
next_state = cpuidle_select(drv, dev);
if (next_state < 0) {
@@ -106,6 +121,10 @@ static int cpuidle_idle_call(void)
goto out;
}
+ /*
+ * The idle task must be scheduled, it is pointless to go to idle,
+ * just update no idle residency and get out of this function
+ */
if (need_resched()) {
dev->last_residency = 0;
/* give the governor an opportunity to reflect on the outcome */
@@ -116,6 +135,12 @@ static int cpuidle_idle_call(void)
trace_cpu_idle_rcuidle(next_state, dev->cpu);
+ /*
+ * Enter the idle state previously returned by the governor
+ * decision. This function will block until an interrupt
+ * occurs and will take care of re-enabling the local
+ * interrupts
+ */
entered_state = cpuidle_enter(drv, dev, next_state);
trace_cpu_idle_rcuidle(PWR_EVENT_EXIT, dev->cpu);
@@ -152,6 +177,10 @@ static void cpu_idle_loop(void)
local_irq_disable();
arch_cpu_idle_enter();
+ /*
+ * It is up to the underlying functions to
+ * enable the local interrupts again
+ */
cpuidle_idle_call();
arch_cpu_idle_exit();
--
1.7.9.5
next prev parent reply other threads:[~2014-02-11 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 15:11 [PATCH 1/5] idle/cpuidle: Split cpuidle_idle_call main function into smaller functions Daniel Lezcano
2014-02-11 15:11 ` [PATCH 2/5] cpuidle/idle: Move the cpuidle_idle_call function to idle.c Daniel Lezcano
2014-02-12 10:43 ` Preeti U Murthy
2014-02-12 12:35 ` Daniel Lezcano
2014-02-11 15:11 ` [PATCH 3/5] idle: Reorganize the idle loop Daniel Lezcano
2014-02-11 17:36 ` Nicolas Pitre
2014-02-12 11:00 ` Preeti U Murthy
2014-02-12 12:45 ` Daniel Lezcano
2014-02-11 15:11 ` [PATCH 4/5] idle: Move idle conditions in cpuidle_idle main function Daniel Lezcano
2014-02-11 15:11 ` Daniel Lezcano [this message]
2014-02-11 17:51 ` [PATCH 5/5] idle: Add more comments to the code Nicolas Pitre
2014-02-11 21:52 ` Daniel Lezcano
2014-02-11 17:27 ` [PATCH 1/5] idle/cpuidle: Split cpuidle_idle_call main function into smaller functions Nicolas Pitre
2014-02-12 10:38 ` Preeti U Murthy
2014-02-12 12:37 ` 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=1392131491-5265-5-git-send-email-daniel.lezcano@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 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®