From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Chen Yu <yu.c.chen@intel.com>, Len Brown <lenb@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Ingo Molnar <mingo@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rui Zhang <rui.zhang@intel.com>
Subject: Re: [PATCH][v2] PM / s2idle: Clear _TIF_POLLING_NRFLAG before suspend to idle
Date: Mon, 22 Jun 2020 19:29:36 +0200 [thread overview]
Message-ID: <20200622172936.GA4781@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJZ5v0gBVBAjdCOXsM-Fa-iAkuv2JMi2mVkG5w7ADcg9dWencA@mail.gmail.com>
On Mon, Jun 22, 2020 at 06:19:35PM +0200, Rafael J. Wysocki wrote:
> > Fixes: b2a02fc43a1f ("smp: Optimize send_call_function_single_ipi()")
> > Suggested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Reported-by: kbuild test robot <lkp@intel.com>
> > Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> > Cc: Len Brown <lenb@kernel.org>
> > Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Signed-off-by: Chen Yu <yu.c.chen@intel.com>
>
> Peter, any more comments here?
Only that the whole s2idle stuff could do with a cleanup :-)
> > +static int call_s2idle(struct cpuidle_driver *drv, struct cpuidle_device *dev,
> > + int index)
> > +{
> > + if (!current_clr_polling_and_test())
> > + s2idle_enter(drv, dev, index);
> > +
> > + return index;
>
> Is the value returned here used at all?
>
> > +}
> > +
> > /**
> > * cpuidle_enter_s2idle - Enter an idle state suitable for suspend-to-idle.
> > * @drv: cpuidle driver for the given CPU.
> > @@ -187,7 +197,7 @@ int cpuidle_enter_s2idle(struct cpuidle_driver *drv, struct cpuidle_device *dev)
> > */
> > index = find_deepest_state(drv, dev, U64_MAX, 0, true);
> > if (index > 0)
> > - enter_s2idle_proper(drv, dev, index);
> > + call_s2idle(drv, dev, index);
>
> I'm wondering why this can't be
>
> if (index > 0 && !current_clr_polling_and_test())
> enter_s2idle_proper(drv, dev, index);
Works for me. Some Wysocki guy wrote much of it, best ask him :-)
The thing that confused me is that all this is way different from the
normal idle path and didn't keep the invariants.
Ideally; much of that gets folded back into the normal patch somehow.
prev parent reply other threads:[~2020-06-22 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 4:04 Chen Yu
2020-06-22 16:19 ` Rafael J. Wysocki
2020-06-22 17:18 ` Chen Yu
2020-06-22 19:45 ` Rafael J. Wysocki
2020-06-23 1:56 ` Chen Yu
2020-06-22 17:29 ` Peter Zijlstra [this message]
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=20200622172936.GA4781@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@intel.com \
/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®