From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Zhang Rui <rui.zhang@intel.com>, Petr Mladek <pmladek@suse.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH v2 2/3] cpuidle: allow setting deepest idle
Date: Tue, 15 Nov 2016 08:52:17 -0800 [thread overview]
Message-ID: <20161115085217.72bec126@jacob-builder> (raw)
In-Reply-To: <7184537.W21RKrGsQO@vostro.rjw.lan>
On Mon, 14 Nov 2016 22:42:03 +0100
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> > diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c
> > index cb6442f..9e80f32 100644
> > --- a/kernel/sched/idle.c
> > +++ b/kernel/sched/idle.c
> > @@ -173,6 +173,9 @@ static void cpuidle_idle_call(void)
> >
> > next_state = cpuidle_find_deepest_state(drv, dev);
> > call_cpuidle(drv, dev, next_state);
> > + } else if (dev->use_deepest_state) {
> > + next_state = cpuidle_find_deepest_state(drv, dev);
> > + call_cpuidle(drv, dev, next_state);
> > } else {
> > /*
> > * Ask the cpuidle framework to choose a
> > convenient idle state.
>
> I would arrange the code slightly differently here:
>
> if (idle_should_freeze() || dev->use_deepest_state) {
> if (idle_should_freeze()) {
> entered_state = cpuidle_enter_freeze(drv,
> dev); if (entered_state > 0) {
> local_irq_enable();
> goto exit_idle;
> }
> }
>
> next_state = cpuidle_find_deepest_state(drv, dev);
> call_cpuidle(drv, dev, next_state);
> } else {
>
>
> This way you'd avoid the ugly code duplication and the extra
> dev->use_deepest_state branch in the most frequent case. I guess you
> could take the unlikely() thing away from idle_should_freeze() and
> use it directly here too.
Sounds good. Will change in the next version.
next prev parent reply other threads:[~2016-11-15 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 18:47 [PATCH v2 0/3] Stop sched tick in idle injection task Jacob Pan
2016-11-14 18:47 ` [PATCH v2 1/3] idle: add support for tasks that inject idle Jacob Pan
2016-11-14 18:47 ` [PATCH v2 2/3] cpuidle: allow setting deepest idle Jacob Pan
2016-11-14 21:42 ` Rafael J. Wysocki
2016-11-15 16:52 ` Jacob Pan [this message]
2016-11-14 18:47 ` [PATCH v2 3/3] thermal/powerclamp: stop sched tick in forced idle Jacob Pan
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=20161115085217.72bec126@jacob-builder \
--to=jacob.jun.pan@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=edubezval@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).