From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Dirk Brandewie <dirk.brandewie@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] Documentation: add ABI entry for intel_pstate
Date: Mon, 06 Jan 2014 12:23:21 +0100 [thread overview]
Message-ID: <7285568.L7MucgKD21@vostro.rjw.lan> (raw)
In-Reply-To: <1388997077-25138-1-git-send-email-artagnon@gmail.com>
On Monday, January 06, 2014 02:01:17 PM Ramkumar Ramachandra wrote:
> Add a Documentation/ABI entry for
> /sys/devices/system/cpu/intel_pstate/max_perf_pct,
> /sys/devices/system/cpu/intel_pstate/min_perf_pct, and
> /sys/devices/system/cpu/intel_pstate/no_turbo.
>
> Cc: Dirk Brandewie <dirk.brandewie@gmail.com>
> Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> Cc: Randy Dunlap <rdunlap@infradead.org>
> Cc: Linux PM <linux-pm@vger.kernel.org>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
> Documentation/ABI/testing/sysfs-devices-system-cpu | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
> index 468e4d4..7080718 100644
> --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
> +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
> @@ -200,3 +200,18 @@ Description: address and size of the percpu note.
> note of cpu#.
>
> crash_notes_size: size of the note of cpu#.
> +
> +
> +What: /sys/devices/system/cpu/intel_pstate/max_perf_pct
> + /sys/devices/system/cpu/intel_pstate/min_perf_pct
> + /sys/devices/system/cpu/intel_pstate/no_turbo
Well, can you please describe each of them separately? Like what each of them
actually does?
> +Date: February 2013
> +Contact: linux-pm@vger.kernel.org
> +Description: Parameters for the Intel P-state driver
> +
> + Logic for selecting the current P-state in Intel
> + Sandybridge+ processors. The three knobs control
> + limits for the P-state that will be requested by the
> + driver.
> +
> + More details can be found in Documentation/cpu-freq/intel-pstate.txt
No, that's not enough.
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2014-01-06 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 8:31 Ramkumar Ramachandra
2014-01-06 11:23 ` Rafael J. Wysocki [this message]
2014-01-06 12:54 ` [PATCH v2] " Ramkumar Ramachandra
2014-01-06 14:33 ` Rafael J. Wysocki
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=7285568.L7MucgKD21@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=artagnon@gmail.com \
--cc=dirk.brandewie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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
all inboxes | Powered by JetHome®