From: Mike Galbraith <efault@gmx.de>
To: Alex Shi <alex.shi@linaro.org>, Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>
Subject: Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration
Date: Wed, 22 Feb 2017 16:03:43 +0100 [thread overview]
Message-ID: <1487775823.4487.23.camel@gmx.de> (raw)
In-Reply-To: <08cafc1b-3e0f-ab48-da45-8ba591379635@linaro.org>
On Wed, 2017-02-22 at 22:53 +0800, Alex Shi wrote:
> cc Rafael.
>
>
> On 02/22/2017 09:12 PM, Peter Zijlstra wrote:
> > On Wed, Feb 22, 2017 at 01:56:37PM +0100, Mike Galbraith wrote:
> > > Hi,
> > >
> > > Do we really need a spinlock for that in the idle loop?
> >
> > Urgh, that's broken on RT, you cannot schedule the idle loop.
> >
> > Also, yeah, reading a s32 should not need no locking, but there's a
> > bunch of pointer chases in between :/
>
> Do you mean s/should not/should/ ? :)
>
> Yes, the dev_pm_qos_read_value() using a power.lock, that is right for normal device.
> But as to this cpu here, the lock isn't necessary.
>
> Hi Rafael,
> Is this fix ok?
That's what I was gonna do, but then figured RT users will take full
control when it really matters, so took the zero added cycles option
for RT instead.
> ===========
> diff --git a/drivers/cpuidle/governors/menu.c b/drivers/cpuidle/governors/menu.c
> index 8d6d25c..957c56d 100644
> --- a/drivers/cpuidle/governors/menu.c
> +++ b/drivers/cpuidle/governors/menu.c
> @@ -273,6 +273,14 @@ static unsigned int get_typical_interval(struct menu_device *data)
> > > goto again;
> }
>
> +int read_this_cpu_resume_latency(int cpu)
> +{
> +> > struct device *dev = get_cpu_device(cpu);
> +
> +> > return IS_ERR_OR_NULL(dev->power.qos) ?
> +> > > 0 : pm_qos_read_value(&dev->power.qos->resume_latency);
> +}
> +
> /**
> * menu_select - selects the next idle state to enter
> * @drv: cpuidle driver containing state data
> @@ -281,13 +289,12 @@ static unsigned int get_typical_interval(struct menu_device *data)
> static int menu_select(struct cpuidle_driver *drv, struct cpuidle_device *dev)
> {
> > > struct menu_device *data = this_cpu_ptr(&menu_devices);
> -> > struct device *device = get_cpu_device(dev->cpu);
> > > int latency_req = pm_qos_request(PM_QOS_CPU_DMA_LATENCY);
> > > int i;
> > > 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 = read_this_cpu_resume_latency(dev->cpu);
>
> > > if (data->needs_update) {
> > > > menu_update(drv, dev);
next prev parent reply other threads:[~2017-02-22 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 12:56 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration Mike Galbraith
2017-02-22 13:12 ` Peter Zijlstra
2017-02-22 13:19 ` Mike Galbraith
2017-02-22 14:31 ` Alex Shi
2017-02-22 14:39 ` Peter Zijlstra
2017-02-22 14:55 ` Alex Shi
2017-02-23 12:15 ` Rafael J. Wysocki
2017-02-23 13:08 ` Mike Galbraith
2017-02-23 13:58 ` Alex Shi
2017-02-23 13:55 ` Alex Shi
2017-02-23 22:34 ` Rafael J. Wysocki
2017-02-24 1:49 ` Alex Shi
2017-02-24 12:25 ` [PATCH] cpuidle: menu: Avoid taking spinlock for accessing QoS values Rafael J. Wysocki
2017-02-22 14:46 ` 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency consideration Mike Galbraith
2017-02-22 14:53 ` Alex Shi
2017-02-22 15:03 ` Mike Galbraith [this message]
2017-02-22 15:36 ` Alex Shi
2017-02-22 15:46 ` Mike Galbraith
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=1487775823.4487.23.camel@gmx.de \
--to=efault@gmx.de \
--cc=alex.shi@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@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