From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] sched/idle : find the best idle CPU with cpuidle info
Date: Thu, 11 Sep 2014 00:50:34 +0200 [thread overview]
Message-ID: <4753245.VagS0oaVYJ@vostro.rjw.lan> (raw)
In-Reply-To: <alpine.LFD.2.11.1409101734470.16533@knanqh.ubzr>
On Wednesday, September 10, 2014 05:35:27 PM Nicolas Pitre wrote:
>
> Ping.
Is this urgent, and if so, then why?
> On Thu, 4 Sep 2014, Nicolas Pitre wrote:
>
> > This is a rework of the series initially posted by Daniel Lezcano here:
> >
> > http://news.gmane.org/group/gmane.linux.power-management.general/thread=44161
> >
> > Those patches were straightened up, commit logs are more comprehensive,
> > bugs were fixed, etc.
> >
> >
> > drivers/cpuidle/cpuidle.c | 6 ++++++
> > kernel/sched/fair.c | 43 ++++++++++++++++++++++++++++++++++-------
> > kernel/sched/idle.c | 6 ++++++
> > kernel/sched/sched.h | 39 +++++++++++++++++++++++++++++++++++++
> > 4 files changed, 87 insertions(+), 7 deletions(-)
> >
> >
> > Nicolas
> >
> >
> > _______________________________________________
> > linaro-kernel mailing list
> > linaro-kernel@lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-kernel
> >
> >
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-09-10 22:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 15:32 Nicolas Pitre
2014-09-04 15:32 ` [PATCH v2 1/2] sched: let the scheduler see CPU idle states Nicolas Pitre
2014-09-18 17:37 ` Paul E. McKenney
2014-09-18 17:39 ` Paul E. McKenney
2014-09-18 23:15 ` Peter Zijlstra
2014-09-18 18:32 ` Nicolas Pitre
2014-09-18 23:17 ` Peter Zijlstra
2014-09-18 23:28 ` Peter Zijlstra
2014-09-19 18:30 ` Nicolas Pitre
2014-09-04 15:32 ` [PATCH v2 2/2] sched/fair: leverage the idle state info when choosing the "idlest" cpu Nicolas Pitre
2014-09-05 7:52 ` Daniel Lezcano
2014-09-18 23:46 ` Peter Zijlstra
2014-09-19 0:05 ` Peter Zijlstra
2014-09-19 4:49 ` Yao Dongdong
2014-09-30 21:58 ` Rik van Riel
2014-09-30 23:15 ` Nicolas Pitre
2014-10-02 17:15 ` [PATCH RFC] sched,idle: teach select_idle_sibling about idle states Rik van Riel
2014-10-03 6:04 ` Mike Galbraith
2014-10-03 6:23 ` Mike Galbraith
2014-10-03 7:50 ` Peter Zijlstra
2014-10-03 13:05 ` Mike Galbraith
2014-10-03 14:28 ` Rik van Riel
2014-10-03 14:46 ` Peter Zijlstra
2014-10-03 15:37 ` Rik van Riel
2014-10-09 16:04 ` Peter Zijlstra
2014-10-03 18:52 ` Nicolas Pitre
2014-09-10 21:35 ` [PATCH v2 0/2] sched/idle : find the best idle CPU with cpuidle info Nicolas Pitre
2014-09-10 22:50 ` Rafael J. Wysocki [this message]
2014-09-10 23:25 ` Nicolas Pitre
2014-09-10 23:28 ` Nicolas Pitre
2014-09-10 23:50 ` Rafael J. Wysocki
2014-09-18 0:39 ` Nicolas Pitre
2014-09-18 23:24 ` Peter Zijlstra
2014-09-19 18:22 ` Nicolas Pitre
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=4753245.VagS0oaVYJ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®