From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: peterz@infradead.org, mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, rjw@rjwysocki.net,
linux-pm@vger.kernel.org, alex.shi@linaro.org,
vincent.guittot@linaro.org, morten.rasmussen@arm.com,
linaro-kernel@lists.linaro.org
Subject: [PATCH 0/3] sched: idle: Provide the basis to integrate cpuidle
Date: Thu, 24 Apr 2014 14:24:48 +0200 [thread overview]
Message-ID: <1398342291-16322-1-git-send-email-daniel.lezcano@linaro.org> (raw)
This patchset provides three patches for the basis to integrate cpuidle with
the scheduler.
The first patch is a cleanup.
The second one adds the sched balance option as requested by Ingo.
The third one stores the idle state a cpu is and adds a rcu_barrier() to
prevent races when using the pointed object.
This patchset is based on top of v3.15-rc2.
This patchset does not modify the behavior of the scheduler.
Taking into account the cpuidle information from the scheduler will be
posted in a separate patchset in order to keep focused on the right decisions
the scheduler should take regarding the policy vs idle parameters.
Daniel Lezcano (3):
sched: idle: Encapsulate the code to compile it out
sched: idle: Add sched balance option
sched: idle: Store the idle state the cpu is
drivers/cpuidle/cpuidle.c | 6 ++
include/linux/sched/sysctl.h | 14 ++++
kernel/sched/fair.c | 92 ++++++++++++++++++++++-
kernel/sched/idle.c | 169 +++++++++++++++++++++++-------------------
kernel/sched/sched.h | 5 ++
kernel/sysctl.c | 11 +++
6 files changed, 220 insertions(+), 77 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-04-24 12:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 12:24 Daniel Lezcano [this message]
2014-04-24 12:24 ` [PATCH 1/3] sched: idle: Encapsulate the code to compile it out Daniel Lezcano
2014-04-30 17:39 ` Nicolas Pitre
2014-04-24 12:24 ` [PATCH 2/3] sched: idle: Add sched balance option Daniel Lezcano
[not found] ` <CAP245DX9wewQFhcyGj5ZuNE7hHC4fRn90POC32HLF6ugja6nJg@mail.gmail.com>
2014-04-24 13:30 ` Daniel Lezcano
2014-04-25 10:54 ` Amit Kucheria
2014-04-25 11:46 ` Rafael J. Wysocki
2014-04-25 12:17 ` Daniel Lezcano
2014-04-25 13:20 ` Peter Zijlstra
2014-04-25 17:01 ` Daniel Lezcano
2014-04-25 18:43 ` Peter Zijlstra
2014-04-28 10:09 ` Daniel Lezcano
2014-04-28 10:28 ` Peter Zijlstra
2014-04-28 11:07 ` Daniel Lezcano
2014-04-28 11:21 ` Peter Zijlstra
2014-04-28 23:11 ` Rafael J. Wysocki
2014-04-29 10:00 ` Morten Rasmussen
2014-04-29 22:19 ` Rafael J. Wysocki
2014-04-29 10:25 ` Daniel Lezcano
2014-05-05 0:32 ` Rafael J. Wysocki
2014-04-29 9:26 ` Morten Rasmussen
2014-04-26 0:18 ` Rafael J. Wysocki
2014-04-26 6:17 ` Ingo Molnar
2014-04-27 13:23 ` Rafael J. Wysocki
2014-04-29 10:50 ` Morten Rasmussen
2014-04-29 22:02 ` Rafael J. Wysocki
2014-04-26 10:55 ` Peter Zijlstra
2014-04-27 13:54 ` Rafael J. Wysocki
2014-04-27 19:39 ` Peter Zijlstra
2014-04-25 13:22 ` Peter Zijlstra
2014-04-24 12:24 ` [PATCH 3/3] sched: idle: Store the idle state the cpu is Daniel Lezcano
2014-04-24 16:16 ` Rafael J. Wysocki
2014-04-24 16:13 ` [PATCH 0/3] sched: idle: Provide the basis to integrate cpuidle 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=1398342291-16322-1-git-send-email-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alex.shi@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--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).