From: Alex Shi <alex.shi@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@redhat.com>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration
Date: Fri, 24 Feb 2017 09:49:25 +0800 [thread overview]
Message-ID: <55ee4ca6-9369-06b5-b680-f6483ca496af@linaro.org> (raw)
In-Reply-To: <2909793.Vfsrmqmg03@aspire.rjw.lan>
> Well, first, please submit this properly (with a proper subject and CC to linux-pm)
> if I'm expected to apply it.
>
Hi Rafael,
Thanks for reminder!
A raw read function looks better. And maybe useful for others.
Acked-by: Alex Shi <alex.shi@linaro.org>
>
>
>
> ---
> drivers/base/power/qos.c | 3 +--
> drivers/cpuidle/governors/menu.c | 2 +-
> include/linux/pm_qos.h | 7 +++++++
> 3 files changed, 9 insertions(+), 3 deletions(-)
>
> Index: linux-pm/drivers/base/power/qos.c
> ===================================================================
> --- linux-pm.orig/drivers/base/power/qos.c
> +++ linux-pm/drivers/base/power/qos.c
> @@ -108,8 +108,7 @@ s32 __dev_pm_qos_read_value(struct devic
> {
> lockdep_assert_held(&dev->power.lock);
>
> - return IS_ERR_OR_NULL(dev->power.qos) ?
> - 0 : pm_qos_read_value(&dev->power.qos->resume_latency);
> + return dev_pm_qos_raw_read_value(dev);
> }
>
> /**
> Index: linux-pm/drivers/cpuidle/governors/menu.c
> ===================================================================
> --- linux-pm.orig/drivers/cpuidle/governors/menu.c
> +++ linux-pm/drivers/cpuidle/governors/menu.c
> @@ -287,7 +287,7 @@ static int menu_select(struct cpuidle_dr
> unsigned int interactivity_req;
> unsigned int expected_interval;
> unsigned long nr_iowaiters, cpu_load;
> - int resume_latency = dev_pm_qos_read_value(device);
> + int resume_latency = dev_pm_qos_raw_read_value(device);
>
> if (data->needs_update) {
> menu_update(drv, dev);
> Index: linux-pm/include/linux/pm_qos.h
> ===================================================================
> --- linux-pm.orig/include/linux/pm_qos.h
> +++ linux-pm/include/linux/pm_qos.h
> @@ -172,6 +172,12 @@ static inline s32 dev_pm_qos_requested_f
> {
> return dev->power.qos->flags_req->data.flr.flags;
> }
> +
> +static inline s32 dev_pm_qos_raw_read_value(struct device *dev)
> +{
> + return IS_ERR_OR_NULL(dev->power.qos) ?
> + 0 : pm_qos_read_value(&dev->power.qos->resume_latency);
> +}
> #else
> static inline enum pm_qos_flags_status __dev_pm_qos_flags(struct device *dev,
> s32 mask)
> @@ -236,6 +242,7 @@ static inline void dev_pm_qos_hide_laten
>
> static inline s32 dev_pm_qos_requested_resume_latency(struct device *dev) { return 0; }
> static inline s32 dev_pm_qos_requested_flags(struct device *dev) { return 0; }
> +static inline s32 dev_pm_qos_raw_read_value(struct device *dev) { return 0; }
> #endif
>
> #endif
>
next prev parent reply other threads:[~2017-02-24 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1487768197.27533.5.camel@gmx.de>
[not found] ` <2050688.jCOqd8xbcD@aspire.rjw.lan>
[not found] ` <e8261472-4338-eab2-98e1-5dd6039899f7@linaro.org>
2017-02-23 22:34 ` 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration Rafael J. Wysocki
2017-02-24 1:49 ` Alex Shi [this message]
2017-02-24 12:25 ` [PATCH] cpuidle: menu: Avoid taking spinlock for accessing QoS values 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=55ee4ca6-9369-06b5-b680-f6483ca496af@linaro.org \
--to=alex.shi@linaro.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
/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).