From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpuidle: Add a predict callback for the governors
Date: Thu, 21 Feb 2019 17:18:25 +0100 [thread overview]
Message-ID: <CAJZ5v0iCkMA=LVvV+-jqr8fCYz2mwaqtiKmNTfxf0dxZ=MvdiQ@mail.gmail.com> (raw)
In-Reply-To: <20190221145631.26356-1-daniel.lezcano@linaro.org>
On Thu, Feb 21, 2019 at 3:56 PM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> Predicting the next event on the current CPU is implemented in the
> idle state selection function, thus the selection logic and the
> prediction are tied together and it is hard to decorrelate both.
>
> The following change introduces the cpuidle function to give the
> opportunity to the governor to store the guess estimate of the
> different source of wakeup and then reuse them in the selection
> process. Consequently we end up with two separate operations clearly
> identified.
>
> As the next events are stored in the cpuidle device structure it is
> easy to propagate them in the different governor callbacks.
Can you explain a bit how you would use this new callback in a governor?
next prev parent reply other threads:[~2019-02-21 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 14:56 [PATCH] cpuidle: Add a predict callback for the governors Daniel Lezcano
2019-02-21 16:18 ` Rafael J. Wysocki [this message]
2019-02-21 17:40 ` Daniel Lezcano
2019-02-22 10:35 ` Rafael J. Wysocki
2019-02-25 15:01 ` Daniel Lezcano
2019-02-26 10:57 ` Rafael J. Wysocki
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='CAJZ5v0iCkMA=LVvV+-jqr8fCYz2mwaqtiKmNTfxf0dxZ=MvdiQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.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).