From: Pavel Machek <pavel@ucw.cz>
To: Venki Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Len Brown <lenb@kernel.org>, Adam Belay <abelay@novell.com>,
Len Brown <len.brown@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Shaohua Li <shaohua.li@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 8/8] cpuidle: first round of documentation updates
Date: Tue, 19 Jun 2007 15:16:27 +0000 [thread overview]
Message-ID: <20070619151626.GA5127@ucw.cz> (raw)
In-Reply-To: <20070606205641.GH23906@linux-os.sc.intel.com>
Hi!
> Documentation changes based on Pavel's feedback.
Thanks!
> -System global cpuidle information are under
> +System global cpuidle related information and tunables are under
> /sys/devices/system/cpu/cpuidle
>
> The current interfaces in this directory has self-explanatory names:
> +* current_driver_ro
> +* current_governor_ro
Uff, the _ro thing looks ugly to my eyes.
> +With cpuidle_sysfs_switch boot option (meant for developer testing)
> +following objects are visible instead.
> * available_drivers
> * available_governors
> * current_driver
> * current_governor
...with different files depending on config it is _very_ ugly.
> More than one governor can be registered at the same time and
> -user can switch between drivers using /sysfs interface.
> +user can switch between drivers using /sysfs interface (when supported).
(when enabled)?
> +More than one governor part is supported for developers to easily experiment
> +with different governors. By default, most optimal governor based on your
delete 'most'?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-06-19 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 20:56 [PATCH 8/8] cpuidle: first round of documentation updates Venki Pallipadi
2007-06-06 21:54 ` Keshavamurthy, Anil S
2007-06-19 15:16 ` Pavel Machek [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=20070619151626.GA5127@ucw.cz \
--to=pavel@ucw.cz \
--cc=abelay@novell.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--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