All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Ingo Molnar <mingo@elte.hu>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Dipankar
Cc: linux-arch@vger.kernel.org, linux-acpi@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [v9 PATCH 0/9]: cpuidle: Cleanup cpuidle/ Introduce cpuidle to POWER.
Date: Fri, 16 Oct 2009 15:08:50 +0530	[thread overview]
Message-ID: <20091016093850.GB27350@linux.vnet.ibm.com> (raw)

Hi,

This patchset introduces cpuidle infrastructure to POWER, prototyping
for pSeries, and also does a major refactoring of current x86 idle
power management and a cleanup of cpuidle infrastructure.

This patch series has been in discussion for quite a while now and
below are the links to the previous discussions.

Hopefully, this is ready to be included in the -tip tree.

v8 --> http://lkml.org/lkml/2009/10/8/82
v7 --> http://lkml.org/lkml/2009/10/6/278
v6 --> http://lkml.org/lkml/2009/9/22/180
v5 --> http://lkml.org/lkml/2009/9/22/26
v4 --> http://lkml.org/lkml/2009/9/1/133
v3 --> http://lkml.org/lkml/2009/8/27/124
v2 --> http://lkml.org/lkml/2009/8/26/233
v1 --> http://lkml.org/lkml/2009/8/19/150


Changes in this version:
----------------------------------------
        *Added documentation for the new design regarding registration
        of idle routines in Documentation/cpuidle/core.txt

        *Platforms which do not want the code bloat of cpuidle can
        disable CONFIG_CPU_IDLE. Alternate definition of
        cpuidle_idle_call is provided which would call the appropriate
        idle routine provided by the arch without the overhead of
        registration and governors.
        (Thanks to Andi for raising this isuue)

        *I had missed a cpuidle_kick_cpus() in
        cpuidle_pause_and_lock() which is called from the hotplug
        path. So added that and tested this patchset by subjecting it
        to cpuhotplug torture.
        (Thanks to Balbir for noticing this)


--arun

WARNING: multiple messages have this Message-ID (diff)
From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Ingo Molnar <mingo@elte.hu>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	Balbir Singh <balbir@in.ibm.com>,
	Andi Kleen <andi@firstfloor.org>,
	Arun Bharadwaj <arun@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-arch@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [v9 PATCH 0/9]: cpuidle: Cleanup cpuidle/ Introduce cpuidle to POWER.
Date: Fri, 16 Oct 2009 15:08:50 +0530	[thread overview]
Message-ID: <20091016093850.GB27350@linux.vnet.ibm.com> (raw)
Message-ID: <20091016093850.vazRs1CU46LyX72OpJsWDYBZ3ZWQkvmtl1kZg3SJ96M@z> (raw)

Hi,

This patchset introduces cpuidle infrastructure to POWER, prototyping
for pSeries, and also does a major refactoring of current x86 idle
power management and a cleanup of cpuidle infrastructure.

This patch series has been in discussion for quite a while now and
below are the links to the previous discussions.

Hopefully, this is ready to be included in the -tip tree.

v8 --> http://lkml.org/lkml/2009/10/8/82
v7 --> http://lkml.org/lkml/2009/10/6/278
v6 --> http://lkml.org/lkml/2009/9/22/180
v5 --> http://lkml.org/lkml/2009/9/22/26
v4 --> http://lkml.org/lkml/2009/9/1/133
v3 --> http://lkml.org/lkml/2009/8/27/124
v2 --> http://lkml.org/lkml/2009/8/26/233
v1 --> http://lkml.org/lkml/2009/8/19/150


Changes in this version:
----------------------------------------
        *Added documentation for the new design regarding registration
        of idle routines in Documentation/cpuidle/core.txt

        *Platforms which do not want the code bloat of cpuidle can
        disable CONFIG_CPU_IDLE. Alternate definition of
        cpuidle_idle_call is provided which would call the appropriate
        idle routine provided by the arch without the overhead of
        registration and governors.
        (Thanks to Andi for raising this isuue)

        *I had missed a cpuidle_kick_cpus() in
        cpuidle_pause_and_lock() which is called from the hotplug
        path. So added that and tested this patchset by subjecting it
        to cpuhotplug torture.
        (Thanks to Balbir for noticing this)


--arun


WARNING: multiple messages have this Message-ID (diff)
From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Ingo Molnar <mingo@elte.hu>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	Balbir Singh <balbir@in.ibm.com>,
	Andi Kleen <andi@firstfloor.org>,
	Arun Bharadwaj <arun@linux.vnet.ibm.com>
Cc: linux-arch@vger.kernel.org, linux-acpi@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [v9 PATCH 0/9]: cpuidle: Cleanup cpuidle/ Introduce cpuidle to POWER.
Date: Fri, 16 Oct 2009 15:08:50 +0530	[thread overview]
Message-ID: <20091016093850.GB27350@linux.vnet.ibm.com> (raw)

Hi,

This patchset introduces cpuidle infrastructure to POWER, prototyping
for pSeries, and also does a major refactoring of current x86 idle
power management and a cleanup of cpuidle infrastructure.

This patch series has been in discussion for quite a while now and
below are the links to the previous discussions.

Hopefully, this is ready to be included in the -tip tree.

v8 --> http://lkml.org/lkml/2009/10/8/82
v7 --> http://lkml.org/lkml/2009/10/6/278
v6 --> http://lkml.org/lkml/2009/9/22/180
v5 --> http://lkml.org/lkml/2009/9/22/26
v4 --> http://lkml.org/lkml/2009/9/1/133
v3 --> http://lkml.org/lkml/2009/8/27/124
v2 --> http://lkml.org/lkml/2009/8/26/233
v1 --> http://lkml.org/lkml/2009/8/19/150


Changes in this version:
----------------------------------------
        *Added documentation for the new design regarding registration
        of idle routines in Documentation/cpuidle/core.txt

        *Platforms which do not want the code bloat of cpuidle can
        disable CONFIG_CPU_IDLE. Alternate definition of
        cpuidle_idle_call is provided which would call the appropriate
        idle routine provided by the arch without the overhead of
        registration and governors.
        (Thanks to Andi for raising this isuue)

        *I had missed a cpuidle_kick_cpus() in
        cpuidle_pause_and_lock() which is called from the hotplug
        path. So added that and tested this patchset by subjecting it
        to cpuhotplug torture.
        (Thanks to Balbir for noticing this)


--arun

             reply	other threads:[~2009-10-16  9:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16  9:38 Arun R Bharadwaj [this message]
2009-10-16  9:38 ` [v9 PATCH 0/9]: cpuidle: Cleanup cpuidle/ Introduce cpuidle to POWER Arun R Bharadwaj
2009-10-16  9:38 ` Arun R Bharadwaj
2009-10-16  9:40 ` [v9 PATCH 1/9]: cpuidle: Design documentation patch Arun R Bharadwaj
2009-10-16  9:40   ` Arun R Bharadwaj
2009-10-16  9:40   ` Arun R Bharadwaj
2009-10-16  9:41 ` [v9 PATCH 2/9]: cpuidle: cleanup drivers/cpuidle/cpuidle.c Arun R Bharadwaj
2009-10-16  9:41   ` Arun R Bharadwaj
2009-10-16  9:41   ` Arun R Bharadwaj
2009-10-16  9:42 ` [v9 PATCH 3/9]: cpuidle: implement a list based approach to register a set of idle routines Arun R Bharadwaj
2009-10-16  9:42   ` Arun R Bharadwaj
2009-10-16  9:42   ` Arun R Bharadwaj
2009-10-16  9:43 ` [v9 PATCH 4/9]: x86: refactor x86 idle power management code and remove all instances of pm_idle Arun R Bharadwaj
2009-10-16  9:43   ` Arun R Bharadwaj
2009-10-16  9:43   ` Arun R Bharadwaj
2009-10-23 16:07   ` Pavel Machek
2009-10-23 16:07     ` Pavel Machek
2009-10-26  7:55     ` Arun R Bharadwaj
2009-10-26  7:55       ` Arun R Bharadwaj
2009-10-26  7:58       ` Pavel Machek
2009-10-26  7:58         ` Pavel Machek
2009-10-26  8:25         ` Arun R Bharadwaj
2009-10-26  8:25           ` Arun R Bharadwaj
2009-10-16  9:44 ` [v9 PATCH 5/9]: POWER: enable cpuidle for POWER Arun R Bharadwaj
2009-10-16  9:44   ` Arun R Bharadwaj
2009-10-16  9:44   ` Arun R Bharadwaj
2009-10-16  9:45 ` [v9 PATCH 6/9]: pSeries/cpuidle: refactor pseries idle loops Arun R Bharadwaj
2009-10-16  9:45   ` Arun R Bharadwaj
2009-10-16  9:45   ` Arun R Bharadwaj
2009-10-16  9:46 ` [v9 PATCH 7/9]: POWER: add a default_idle idle loop for POWER Arun R Bharadwaj
2009-10-16  9:46   ` Arun R Bharadwaj
2009-10-16  9:46   ` Arun R Bharadwaj
2009-10-16  9:47 ` [v9 PATCH 8/9]: pSeries: implement pSeries processor idle module Arun R Bharadwaj
2009-10-16  9:47   ` Arun R Bharadwaj
2009-10-16  9:47   ` Arun R Bharadwaj
2009-10-16  9:48 ` [v9 PATCH 9/9]: POWER: Enable default_idle when power_save=off Arun R Bharadwaj
2009-10-16  9:48   ` Arun R Bharadwaj
2009-10-16  9:48   ` Arun R Bharadwaj
2009-11-16 10:36 ` [v9 PATCH 0/9]: cpuidle: Cleanup cpuidle/ Introduce cpuidle to POWER Arun R Bharadwaj
2009-11-16 10:36   ` Arun R Bharadwaj
2009-11-16 10:36   ` Arun R Bharadwaj

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=20091016093850.GB27350@linux.vnet.ibm.com \
    --to=arun@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=benh@kernel.crashing.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=svaidy@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.