From: Greg Kroah-Hartman <gregkh@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Alex Chiang <achiang@hp.com>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Len Brown <lenb@kernel.org>, Greg Kroah-Hartman <gregkh@suse.de>
Subject: [PATCH 8/9] Documentation: ABI: /sys/devices/system/cpu/cpuidle/
Date: Fri, 30 Oct 2009 15:54:27 -0700 [thread overview]
Message-ID: <1256943268-12164-8-git-send-email-gregkh@suse.de> (raw)
In-Reply-To: <20091030220930.GA11297@kroah.com>
From: Alex Chiang <achiang@hp.com>
Document cpuidle sysfs attributes by reading code, Documentation/cpuidle/,
and git logs.
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Len Brown <lenb@kernel.org>
Signed-off-by: Alex Chiang <achiang@hp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
---
Documentation/ABI/testing/sysfs-devices-system-cpu | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 8cdda1c..968d8ba 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -101,6 +101,26 @@ Description: CPU topology files that describe a logical CPU's relationship
See Documentation/cputopology.txt for more information.
+What: /sys/devices/system/cpu/cpuidle/current_driver
+ /sys/devices/system/cpu/cpuidle/current_governer_ro
+Date: September 2007
+Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
+Description: Discover cpuidle policy and mechanism
+
+ Various CPUs today support multiple idle levels that are
+ differentiated by varying exit latencies and power
+ consumption during idle.
+
+ Idle policy (governor) is differentiated from idle mechanism
+ (driver)
+
+ current_driver: displays current idle mechanism
+
+ current_governor_ro: displays current idle policy
+
+ See files in Documentation/cpuidle/ for more information.
+
+
What: /sys/devices/system/cpu/cpu*/cache/index*/cache_disable_X
Date: August 2008
KernelVersion: 2.6.27
--
1.6.4.2
next prev parent reply other threads:[~2009-10-30 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 22:09 [GIT PATCH] driver core fixes for 2.6.32-git Greg KH
2009-10-30 22:54 ` [PATCH 1/9] Driver core: fix driver_register() return value Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 2/9] Driver core: allow certain drivers prohibit bind/unbind via sysfs Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 3/9] Documentation: ABI: rename sysfs-devices-cache_disable properly Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 4/9] Documentation: ABI: document /sys/devices/system/cpu/ Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 5/9] Documentation: ABI: /sys/devices/system/cpu/ topology files Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 6/9] Documentation: ABI: /sys/devices/system/cpu/cpu#/ " Greg Kroah-Hartman
2009-10-30 22:54 ` [PATCH 7/9] Documentation: ABI: /sys/devices/system/cpu/sched_[mc|smt]_power_savings Greg Kroah-Hartman
2009-10-30 22:54 ` Greg Kroah-Hartman [this message]
2009-10-30 22:54 ` [PATCH 9/9] Documentation: ABI: /sys/devices/system/cpu/cpu#/node Greg Kroah-Hartman
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=1256943268-12164-8-git-send-email-gregkh@suse.de \
--to=gregkh@suse.de \
--cc=achiang@hp.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@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