From: Randy Dunlap <randy.dunlap@oracle.com>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] CPU_IDLE: Documentation for CPU_IDLE
Date: Tue, 12 Feb 2008 20:36:49 -0800 [thread overview]
Message-ID: <47B273E1.70807@oracle.com> (raw)
In-Reply-To: <20080213011552.GA7319@linux-os.sc.intel.com>
Venki Pallipadi wrote:
> Updated reflecting Randy's comments.
>
> Thanks,
> Venki
>
>
> Documentation for cpuidle infrastructure. This patch was submitted once
> a while back. But, somehow got dropped or never made it upstream.
>
> Resending with updates.
>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
>
> Index: linux-2.6.25-rc/Documentation/cpuidle/core.txt
> ===================================================================
> --- /dev/null
> +++ linux-2.6.25-rc/Documentation/cpuidle/core.txt
> @@ -0,0 +1,24 @@
> +
> + Supporting multiple CPU idle levels in kernel
> +
> + cpuidle
> +
> +General Information:
> +
> +Various CPUs today support multiple idle levels that are differentiated
> +by varying exit latencies and power consumption during idle.
> +cpuidle is a generic in-kernel infrastructure that separates
> +idle policy (governor) from idle mechanism (driver) and provides a
> +standardized infrastructure to support independent development of
> +governors and drivers.
> +
> +cpuidle resides under drivers/cpuidle.
> +
> +Boot options:
> +"cpuidle_sysfs_switch"
> +enables current_governor interface in /sys/devices/system/cpu/cpuidle/.
s#cpuidle/.#cpuidle/,#
> +which can be used to switch governors at run time. This boot option
> +is meant for developer testing only. In normal usage, kernel picks the
> +best governor based on governor ratings.
> +SEE ALSO: sysfs.txt in this directory.
Thanks.
--
~Randy
next prev parent reply other threads:[~2008-02-13 4:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 1:55 [PATCH] CPU_IDLE: Documentation for CPU_IDLE Venki Pallipadi
2008-02-12 16:46 ` Randy Dunlap
2008-02-13 1:15 ` Venki Pallipadi
2008-02-13 4:36 ` Randy Dunlap [this message]
2008-02-14 5:16 ` Len Brown
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=47B273E1.70807@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox