From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH V3 2/2] sched: idle: IRQ based next prediction for idle period
Date: Thu, 18 Feb 2016 10:25:54 +0000 [thread overview]
Message-ID: <56C59C32.1000903@linaro.org> (raw)
In-Reply-To: <CAJZ5v0id8+8oWLxDTJhewH3rKFvKPuAzMoOeg4xy2J097yCd9w@mail.gmail.com>
On 02/17/2016 11:21 PM, Rafael J. Wysocki wrote:
[ ... ]
>>> Reviewed-by: Nicolas Pitre <nico@linaro.org>
>>
>> Well, I'm likely overlooking something, but how is this going to be
>> hooked up to the code in idle.c?
>
> My somewhat educated guess is that sched_idle() in your patch is
> intended to replace cpuidle_idle_call(), right?
Well, no. I was planning to first have it to use a different code path
as experimental code in order to focus improving the accuracy of the
prediction and then merge or replace cpuidle_idle_call() with sched_idle().
> If so, why do you want to replace it?
>
> And assuming that you have a good enough reason to do that, you need
> to ensure that suspend-to-idle will work anyway.
Yes, sure.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2016-02-18 10:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 15:43 [PATCH V3 1/2] irq: Track the interrupt timings Daniel Lezcano
2016-02-16 15:43 ` [PATCH V3 2/2] sched: idle: IRQ based next prediction for idle period Daniel Lezcano
2016-02-16 16:44 ` Nicolas Pitre
2016-02-17 23:09 ` Rafael J. Wysocki
2016-02-17 23:21 ` Rafael J. Wysocki
2016-02-18 10:25 ` Daniel Lezcano [this message]
2016-02-18 19:57 ` Rafael J. Wysocki
2016-02-19 15:01 ` Daniel Lezcano
2016-02-19 23:43 ` Rafael J. Wysocki
2016-02-23 9:49 ` Daniel Lezcano
2016-02-22 15:02 ` Shreyas B Prabhu
2016-02-22 17:29 ` Daniel Lezcano
2016-02-23 10:08 ` Shreyas B Prabhu
2016-02-23 10:06 ` Shreyas B Prabhu
2016-02-23 10:13 ` Daniel Lezcano
2016-02-16 16:45 ` [PATCH V3 1/2] irq: Track the interrupt timings Nicolas Pitre
2016-02-22 14:48 ` Shreyas B Prabhu
2016-02-22 17:24 ` Daniel Lezcano
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=56C59C32.1000903@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@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).