From: Arjan van de Ven <arjan@linux.intel.com>
To: Trinabh Gupta <trinabh@linux.vnet.ibm.com>
Cc: peterz@infradead.org, lenb@kernel.org, suresh.b.siddha@intel.com,
benh@kernel.crashing.org, venki@google.com, ak@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC V2 3/3] cpuidle: default idle driver for x86
Date: Thu, 13 Jan 2011 07:47:16 -0800 [thread overview]
Message-ID: <4D2F1E84.2000200@linux.intel.com> (raw)
In-Reply-To: <20110113125223.11174.60425.stgit@tringupt.in.ibm.com>
On 1/13/2011 4:52 AM, Trinabh Gupta wrote:
> This default cpuidle_driver parses idle= boot parameters, selects
> the optimal idle routine for x86 during bootup and registers with
> cpuidle. The code for idle routines and the selection of optimal
> routine is moved from arch/x86/kernel/process.c . At module_init this
> default driver is registered with cpuidle and for non ACPI platforms
> it continues to be used. For ACPI platforms, acpi_idle driver would
> replace this driver at a later point in time during bootup. Until
> this driver's registration, architecture supplied compile time
> default idle routine is called from within cpuidle_idle_call().
>
I like the general approach, but I'd think making idle drivers modular
is going one step too far....
that looks like waaay overkill to me (also since most of the actual idle
handlers are so small
that the overhead of the exported symbols alone is bigger than the idle
handlers)
next prev parent reply other threads:[~2011-01-13 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 12:51 [RFC V2 0/3] cpuidle: Cleanup pm_idle and include driver/cpuidle.c in-kernel Trinabh Gupta
2011-01-13 12:52 ` [RFC V2 1/3] cpuidle: Remove pm_idle pointer for x86 Trinabh Gupta
2011-01-13 12:52 ` [RFC V2 2/3] cpuidle: list based cpuidle driver registration and selection Trinabh Gupta
2011-01-13 12:52 ` [RFC V2 3/3] cpuidle: default idle driver for x86 Trinabh Gupta
2011-01-13 15:47 ` Arjan van de Ven [this message]
2011-01-13 16:22 ` Vaidyanathan Srinivasan
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=4D2F1E84.2000200@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=suresh.b.siddha@intel.com \
--cc=trinabh@linux.vnet.ibm.com \
--cc=venki@google.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.