From: Peter Zijlstra <peterz@infradead.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/9] setting the table for integration of cpuidle with the scheduler
Date: Mon, 27 Jan 2014 12:47:31 +0000 [thread overview]
Message-ID: <20140127124731.GA4941@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1390802904-28399-1-git-send-email-nicolas.pitre@linaro.org>
On Mon, Jan 27, 2014 at 01:08:15AM -0500, Nicolas Pitre wrote:
> As everyone should know by now, we want to integrate the cpuidle
> governor with the scheduler for a more efficient idling of CPUs.
> In order to help the transition, this small patch series moves the
> existing interaction with cpuidle from architecture code to generic
> core code. No functional change should have occurred yet.
>
> The ARM, PPC, SH and X86 architectures are concerned. Small cleanups
> to ARM and ARM64 are also included. I don't know yet the best path for
> those patches to get into mainline, but it is probably best if they
> stay together. So ACKs from architecture maintainers would be greatly
> appreciated.
>
>
> arch/arm/kernel/process.c | 21 +++---------
> arch/arm/kernel/setup.c | 7 ++++
> arch/arm64/kernel/process.c | 5 ---
> arch/arm64/kernel/setup.c | 7 ++++
> arch/powerpc/platforms/pseries/processor_idle.c | 5 +++
> arch/powerpc/platforms/pseries/setup.c | 34 ++++++++-----------
> arch/sh/kernel/idle.c | 4 +--
> arch/x86/kernel/process.c | 5 +--
> include/linux/cpu.h | 1 -
> kernel/Makefile | 1 -
> kernel/cpu/Makefile | 1 -
> kernel/sched/Makefile | 2 +-
> kernel/{cpu => sched}/idle.c | 6 ++--
> 13 files changed, 44 insertions(+), 55 deletions(-)
Thomas, any objections to this? It looks like a sensible thing to do.
prev parent reply other threads:[~2014-01-27 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 6:08 [PATCH 0/9] setting the table for integration of cpuidle with the scheduler Nicolas Pitre
2014-01-27 6:08 ` [PATCH 1/9] ARM: get rid of arch_cpu_idle_prepare() Nicolas Pitre
2014-01-27 8:22 ` Daniel Lezcano
2014-01-27 16:07 ` Russell King - ARM Linux
2014-01-27 17:12 ` Daniel Lezcano
2014-01-27 17:21 ` Russell King - ARM Linux
2014-01-27 17:30 ` Daniel Lezcano
2014-01-27 17:35 ` Peter Zijlstra
2014-01-27 12:45 ` Russell King - ARM Linux
2014-01-27 15:45 ` Nicolas Pitre
2014-01-27 16:06 ` Russell King - ARM Linux
2014-01-27 17:36 ` Nicolas Pitre
2014-01-27 6:08 ` [PATCH 2/9] ARM64: " Nicolas Pitre
2014-01-27 8:23 ` Daniel Lezcano
2014-01-27 15:43 ` Catalin Marinas
2014-01-27 15:51 ` Nicolas Pitre
2014-01-27 15:57 ` Catalin Marinas
2014-01-27 6:08 ` [PATCH 3/9] idle: no more arch_cpu_idle_prepare() users Nicolas Pitre
2014-01-27 8:24 ` Daniel Lezcano
2014-01-27 6:08 ` [PATCH 4/9] idle: move the cpuidle entry point to the generic idle loop Nicolas Pitre
2014-01-27 8:32 ` Daniel Lezcano
2014-01-27 6:08 ` [PATCH 5/9] ARM: remove redundant cpuidle_idle_call() Nicolas Pitre
2014-01-27 8:33 ` Daniel Lezcano
2014-01-27 6:08 ` [PATCH 6/9] PPC: " Nicolas Pitre
2014-01-27 8:35 ` Daniel Lezcano
2014-01-27 12:11 ` Preeti U Murthy
2014-01-27 6:08 ` [PATCH 7/9] SH: " Nicolas Pitre
2014-01-27 8:35 ` Daniel Lezcano
2014-01-27 6:08 ` [PATCH 8/9] X86: " Nicolas Pitre
2014-01-27 8:43 ` Daniel Lezcano
2014-01-27 6:08 ` [PATCH 9/9] cpu/idle.c: move to sched/idle.c Nicolas Pitre
2014-01-27 12:47 ` Peter Zijlstra [this message]
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=20140127124731.GA4941@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).