From: Ramesh Thomas <ramesh.thomas@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Tero Kristo <t-kristo@ti.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Alex Shi <alex.shi@linaro.org>
Subject: Re: [RFT][PATCH 1/2] PM / domains: Rework governor code to be more consistent
Date: Fri, 3 Nov 2017 00:05:02 -0700 [thread overview]
Message-ID: <20171103070501.GA22692@intel.com> (raw)
In-Reply-To: <2099930.xGFd9X30dN@aspire.rjw.lan>
On 2017-11-02 at 00:01:50 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The genpd governor currently uses negative PM QoS values to indicate
> the "no suspend" condition and 0 as "no restriction", but it doesn't
> use them consistently. Moreover, it tries to refresh QoS values for
> already suspended devices in a quite questionable way.
>
> For the above reasons, rework it to be a bit more consistent.
>
> First off, note that dev_pm_qos_read_value() in
> dev_update_qos_constraint() and __default_power_down_ok() is
> evaluated for devices in suspend. Moreover, that only happens if the
> effective_constraint_ns value for them is negative (meaning "no
> suspend"). It is not evaluated in any other cases, so effectively
> the QoS values are only updated for devices in suspend that should
> not have been suspended in the first place. In all of the other
> cases, the QoS values taken into account are the effective ones from
> the time before the device has been suspended, so generally devices
> need to be resumed and suspended again for new QoS values to take
> effect anyway. Thus evaluating dev_update_qos_constraint() in
> those two places doesn't make sense at all, so drop it.
>
> Second, initialize effective_constraint_ns to 0 ("no constraint")
> rather than to (-1) ("no suspend"), which makes more sense in
> general and in case effective_constraint_ns is never updated
> (the device is in suspend all the time or it is never suspended)
> it doesn't affect the device's parent and so on.
>
> Finally, rework default_suspend_ok() to explicitly handle the
> "no restriction" and "no suspend" special cases.
>
> Also add WARN_ON() around checks that should never trigger.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/base/power/domain.c | 2 -
> drivers/base/power/domain_governor.c | 56 ++++++++++++++++++++---------------
> 2 files changed, 33 insertions(+), 25 deletions(-)
>
> Index: linux-pm/drivers/base/power/domain.c
> ===================================================================
> --- linux-pm.orig/drivers/base/power/domain.c
> +++ linux-pm/drivers/base/power/domain.c
> @@ -1331,7 +1331,7 @@ static struct generic_pm_domain_data *ge
>
> gpd_data->base.dev = dev;
> gpd_data->td.constraint_changed = true;
> - gpd_data->td.effective_constraint_ns = -1;
> + gpd_data->td.effective_constraint_ns = 0;
> gpd_data->nb.notifier_call = genpd_dev_pm_qos_notifier;
>
> spin_lock_irq(&dev->power.lock);
> Index: linux-pm/drivers/base/power/domain_governor.c
> ===================================================================
> --- linux-pm.orig/drivers/base/power/domain_governor.c
> +++ linux-pm/drivers/base/power/domain_governor.c
> @@ -14,22 +14,22 @@
> static int dev_update_qos_constraint(struct device *dev, void *data)
> {
> s64 *constraint_ns_p = data;
> - s32 constraint_ns = -1;
> -
> - if (dev->power.subsys_data && dev->power.subsys_data->domain_data)
> - constraint_ns = dev_gpd_data(dev)->td.effective_constraint_ns;
> + s64 constraint_ns;
>
> - if (constraint_ns < 0) {
> - constraint_ns = dev_pm_qos_read_value(dev);
> - constraint_ns *= NSEC_PER_USEC;
> - }
> - if (constraint_ns == 0)
> + if (!dev->power.subsys_data || !dev->power.subsys_data->domain_data)
> return 0;
>
> /*
> - * constraint_ns cannot be negative here, because the device has been
> - * suspended.
> + * Only take suspend-time QoS constraints of devices into account,
> + * because constraints updated after the device has been suspended are
> + * not guaranteed to be taken into account anyway. In order for them
> + * to take effect, the device has to be resumed and suspended again.
> */
> + constraint_ns = dev_gpd_data(dev)->td.effective_constraint_ns;
> + /* 0 means "no constraint" */
> + if (constraint_ns == 0)
> + return 0;
> +
> if (constraint_ns < *constraint_ns_p || *constraint_ns_p == 0)
> *constraint_ns_p = constraint_ns;
>
> @@ -76,14 +76,26 @@ static bool default_suspend_ok(struct de
> device_for_each_child(dev, &constraint_ns,
> dev_update_qos_constraint);
>
> - if (constraint_ns > 0) {
> + if (constraint_ns == 0) {
> + /* "No restriction", so the device is allowed to suspend. */
> + td->effective_constraint_ns = 0;
> + td->cached_suspend_ok = true;
> + } else if (WARN_ON(constraint_ns < 0)) {
Should never comer here. Child should not have suspended.
Should be a fatal bug. This else block probably is not necessary.
> + /*
> + * effective_constraint_ns is negative already and
> + * cached_suspend_ok is false, so return right away.
> + */
> + return false;
> + } else {
> constraint_ns -= td->suspend_latency_ns +
> td->resume_latency_ns;
> - if (constraint_ns == 0)
> + /* Again, if negative or zero, returning right away is fine. */
> + if (constraint_ns <= 0)
> return false;
> +
> + td->effective_constraint_ns = constraint_ns;
> + td->cached_suspend_ok = true;
> }
> - td->effective_constraint_ns = constraint_ns;
> - td->cached_suspend_ok = constraint_ns >= 0;
>
> /*
> * The children have been suspended already, so we don't need to take
> @@ -144,18 +156,14 @@ static bool __default_power_down_ok(stru
> */
> td = &to_gpd_data(pdd)->td;
> constraint_ns = td->effective_constraint_ns;
> - /* default_suspend_ok() need not be called before us. */
> - if (constraint_ns < 0) {
> - constraint_ns = dev_pm_qos_read_value(pdd->dev);
> - constraint_ns *= NSEC_PER_USEC;
> - }
> + /* Negative values mean "no suspend at all" */
> + if (WARN_ON(constraint_ns < 0))
> + return false;
Cannot come here if was not suspended. Looks like a redundant check.
> +
> + /* 0 means "no constraint" */
> if (constraint_ns == 0)
> continue;
>
> - /*
> - * constraint_ns cannot be negative here, because the device has
> - * been suspended.
> - */
> if (constraint_ns <= off_on_time_ns)
> return false;
>
>
next prev parent reply other threads:[~2017-11-03 7:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 23:00 [RFT][PATCH 0/2] PM / QoS: Device resume latency framework fix Rafael J. Wysocki
2017-11-01 23:01 ` [RFT][PATCH 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-03 7:05 ` Ramesh Thomas [this message]
2017-11-03 7:51 ` Rafael J. Wysocki
2017-11-01 23:03 ` [RFT][PATCH 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-03 7:43 ` Ramesh Thomas
2017-11-03 7:58 ` Rafael J. Wysocki
2017-11-03 10:38 ` Rafael J. Wysocki
2017-11-03 11:42 ` [RFT][PATCH v2 0/2] PM / QoS: Device resume latency framework fix Rafael J. Wysocki
2017-11-03 11:47 ` [RFT][PATCH v2 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-04 2:34 ` Ramesh Thomas
2017-11-04 11:24 ` Rafael J. Wysocki
2017-11-06 7:47 ` Ramesh Thomas
2017-11-06 12:10 ` Ulf Hansson
2017-11-06 12:34 ` Rafael J. Wysocki
2017-11-06 12:44 ` Ulf Hansson
2017-11-06 12:49 ` Rafael J. Wysocki
2017-11-06 14:38 ` Ulf Hansson
2017-11-06 23:07 ` Rafael J. Wysocki
2017-11-03 11:50 ` [RFT][PATCH v2 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-03 16:39 ` Reinette Chatre
2017-11-04 2:28 ` Ramesh Thomas
2017-11-04 11:30 ` Rafael J. Wysocki
2017-11-04 11:58 ` Rafael J. Wysocki
2017-11-04 11:28 ` Rafael J. Wysocki
2017-11-04 2:38 ` Ramesh Thomas
2017-11-04 12:34 ` [RFT][Update][PATCH " Rafael J. Wysocki
2017-11-06 17:47 ` Reinette Chatre
2017-11-07 1:07 ` Rafael J. Wysocki
2017-11-06 13:46 ` [RFT][PATCH v2 0/2] PM / QoS: Device resume latency framework fix Geert Uytterhoeven
2017-11-07 1:08 ` Rafael J. Wysocki
2017-11-08 9:09 ` Tero Kristo
2017-11-07 1:17 ` [PATCH v3 " Rafael J. Wysocki
2017-11-07 1:23 ` [PATCH v3 1/2] PM / domains: Rework governor code to be more consistent Rafael J. Wysocki
2017-11-07 5:05 ` Ramesh Thomas
2017-11-07 10:22 ` Rafael J. Wysocki
2017-11-07 23:24 ` Ramesh Thomas
2017-11-10 7:49 ` Ulf Hansson
2017-11-07 1:27 ` [PATCH v3 2/2] PM / QoS: Fix device resume latency framework Rafael J. Wysocki
2017-11-07 4:33 ` Ramesh Thomas
2017-11-07 10:12 ` Rafael J. Wysocki
2017-11-07 10:33 ` [PATCH v4 " Rafael J. Wysocki
2017-11-07 23:15 ` Ramesh Thomas
2017-11-08 0:09 ` Rafael J. Wysocki
2017-11-10 7:49 ` Ulf Hansson
2017-11-10 8:03 ` Geert Uytterhoeven
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=20171103070501.GA22692@intel.com \
--to=ramesh.thomas@intel.com \
--cc=alex.shi@linaro.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=rjw@rjwysocki.net \
--cc=t-kristo@ti.com \
--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).