From: Natesh Sharma <nsharma@redhat.com>
To: corbet@lwn.net, chenhuacai@kernel.org,
dave.hansen@linux.intel.com, geert@linux-m68k.org,
axboe@kernel.dk, linux@zary.sk
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Natesh Sharma <nsharma@redhat.com>
Subject: [PATCH] docs: admin-guide: Add information about intel_pstate active mode
Date: Mon, 1 May 2023 13:50:50 +0530 [thread overview]
Message-ID: <20230501082050.74131-1-nsharma@redhat.com> (raw)
Information about intel_pstate active mode is added in the doc.
This operation mode could be used to set on the hardware when it's
not activated. Status of the mode could be checked from sysfs file
i.e., /sys/devices/system/cpu/intel_pstate/status.
The information is already available in cpu-freq/intel-pstate.txt
documentation.
Link: https://www.kernel.org/doc/Documentation/cpu-freq/intel-pstate.txt
Signed-off-by: Natesh Sharma <nsharma@redhat.com>
---
Documentation/admin-guide/kernel-parameters.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index bbecbd5797a3..10f3c8d1bb46 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -2104,6 +2104,14 @@
disable
Do not enable intel_pstate as the default
scaling driver for the supported processors
+ active
+ Use intel_pstate driver to bypass the scaling governors
+ layer of cpufreq and provides it own algorithms for p-state
+ selection. There are two P-state selection algorithms provided
+ by intel_pstate in the active mode: powersave and performance.
+ The way they both operate depends on whether or not the hardware
+ managed P-states (HWP) feature has been enabled in the processor
+ and possibly on the processor model.
passive
Use intel_pstate as a scaling driver, but configure it
to work with generic cpufreq governors (instead of
--
2.39.2 (Apple Git-143)
next reply other threads:[~2023-05-01 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 8:20 Natesh Sharma [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-27 8:37 Natesh Sharma
[not found] ` <CACY8qCSVcLkDGWCVmZ9-fhaax7FQdY=FS4MGyy_-wo3Qc_CSig@mail.gmail.com>
2023-05-01 13:17 ` Jonathan Corbet
2023-05-19 14:36 ` Jonathan Corbet
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=20230501082050.74131-1-nsharma@redhat.com \
--to=nsharma@redhat.com \
--cc=axboe@kernel.dk \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
/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®