From: Mark Pearson <markpearson@lenovo.com>
To: <markpearson@lenovo.com>
Cc: <dvhart@infradead.org>, <mgross@linux.intel.com>,
<mario.limonciello@dell.com>, <eliadevito@gmail.com>,
<hadess@hadess.net>, <bberg@redhat.com>,
<linux-pm@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: [PATCH] [RFC] Documentation: Add documentation for new platform_profile sysfs attribute
Date: Mon, 26 Oct 2020 13:44:44 -0400 [thread overview]
Message-ID: <20201026174444.866545-1-markpearson@lenovo.com> (raw)
In-Reply-To: <markpearson@lenovo.com>
From: Hans de Goede <hdegoede@redhat.com>
On modern systems the platform performance, temperature, fan and other
hardware related characteristics are often dynamically configurable. The
profile is often automatically adjusted to the load by somei
automatic-mechanism (which may very well live outside the kernel).
These auto platform-adjustment mechanisms often can be configured with
one of several 'platform-profiles', with either a bias towards low-power
consumption or towards performance (and higher power consumption and
thermals).
Introduce a new platform_profile sysfs API which offers a generic API for
selecting the performance-profile of these automatic-mechanisms.
Co-developed-by: Mark Pearson <markpearson@lenovo.com>
Signed-off-by: Mark Pearson <markpearson@lenovo.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
.../ABI/testing/sysfs-platform_profile | 85 +++++++++++++++++++
1 file changed, 85 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-platform_profile
diff --git a/Documentation/ABI/testing/sysfs-platform_profile b/Documentation/ABI/testing/sysfs-platform_profile
new file mode 100644
index 000000000000..37cb6275946c
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-platform_profile
@@ -0,0 +1,85 @@
+Platform-profile selection (e.g. /sys/firmware/acpi/platform_profile)
+
+On modern systems the platform performance, temperature, fan and other
+hardware related characteristics are often dynamically configurable. The
+profile is often automatically adjusted to the load by some
+automatic-mechanism (which may very well live outside the kernel).
+
+These auto platform-adjustment mechanisms often can be configured with
+one of several 'platform-profiles', with either a bias towards low-power
+consumption or towards performance (and higher power consumption and
+thermals).
+
+The purpose of the platform_profile attribute is to offer a generic sysfs
+API for selecting the platform-profile of these automatic-mechanisms.
+
+Note that this API is only for selecting the platform-profile, it is
+NOT a goal of this API to allow monitoring the resulting performance
+characteristics. Monitoring performance is best done with device/vendor
+specific tools such as e.g. turbostat.
+
+Specifically when selecting a high-performance profile the actual achieved
+performance may be limited by various factors such as: the heat generated
+by other components, room temperature, free air flow at the bottom of a
+laptop, etc. It is explicitly NOT a goal of this API to let userspace know
+about any sub-optimal conditions which are impeding reaching the requested
+performance level.
+
+Since numbers are a rather meaningless way to describe platform-profiles
+this API uses strings to describe the various profiles. To make sure that
+userspace gets a consistent experience when using this API this API
+document defines a fixed set of profile-names. Drivers *must* map their
+internal profile representation/names onto this fixed set.
+
+If for some reason there is no good match when mapping then a new profile-name
+may be added. Drivers which wish to introduce new profile-names must:
+1. Have very good reasons to do so.
+2. Add the new profile-name to this document, so that future drivers which also
+ have a similar problem can use the same new. Usually new profile-names will
+ be added to the "extra profile-names" section of this document. But in some
+ cases the set of standard profile-names may be extended.
+
+What: /sys/firmware/acpi/platform_profile_choices
+Date: October 2020
+Contact: Hans de Goede <hdegoede@redhat.com>
+Description:
+ Reading this file gives a space separated list of profiles
+ supported for this device.
+
+ Drivers must use the following standard profile-names whenever
+ possible:
+
+ low-power: Emphasises low power consumption
+ quiet: Offers quieter operation (lower fan
+ speed but with higher performance and
+ temperatures then seen in low-power
+ balanced: Balance between low power consumption
+ and performance
+ performance: Emphasises performance (and may lead to
+ higher temperatures and fan speeds)
+
+ Userspace may expect drivers to offer at least several of these
+ standard profile-names! If none of the above are a good match
+ for some of the drivers profiles, then drivers may use one of
+ these extra profile-names:
+ <reserved for future use>
+
+What: /sys/firmware/acpi/platform_profile
+Date: October 2020
+Contact: Hans de Goede <hdegoede@redhat.com>
+Description:
+ Reading this file gives the current selected profile for this
+ device. Writing this file with one of the strings from
+ available_profiles changes the profile to the new value.
+
+ Reading this file may also return "custom". This is intended for
+ drivers which have and export multiple knobs. Such drivers may
+ very well still want to offer a set of profiles for easy of use
+ and to be able to offer a consistent standard API (this API) to
+ userspace for configuring their performance. The "custom" value
+ is intended for when ai user has directly configured the knobs
+ (through e.g. some advanced control-panel for a GPU) and the
+ knob values do not match any of the presets represented by the
+ platform-profiles. In this case writing this file will
+ override the modifications and restore the selected presets.
+
--
2.28.0
next reply other threads:[~2020-10-26 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 17:44 Mark Pearson [this message]
2020-10-26 18:33 ` [PATCH] [RFC] Documentation: Add documentation for new platform_profile sysfs attribute Hans de Goede
2020-10-26 18:33 ` Hans de Goede
2020-10-26 19:55 ` [External] " Mark Pearson
2020-10-27 7:54 ` Hans de Goede
2020-10-27 9:19 ` Elia Devito
2020-10-27 12:28 ` Mark Pearson
2020-10-27 13:41 ` Hans de Goede
2020-10-27 15:01 ` Mark Pearson
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=20201026174444.866545-1-markpearson@lenovo.com \
--to=markpearson@lenovo.com \
--cc=bberg@redhat.com \
--cc=dvhart@infradead.org \
--cc=eliadevito@gmail.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.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