From: Benjamin Berg <bberg@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Mark Gross <mgross@linux.intel.com>
Cc: Mario Limonciello <mario.limonciello@dell.com>,
Mark Pearson <mpearson@lenovo.com>,
Elia Devito <eliadevito@gmail.com>,
Bastien Nocera <hadess@hadess.net>,
linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mark Pearson <markpearson@lenovo.com>
Subject: Re: [RFC] Documentation: Add documentation for new performance_profile sysfs class
Date: Mon, 05 Oct 2020 15:13:44 +0200 [thread overview]
Message-ID: <c464996fb3e0e23958c01196fe45f79cafce6cf4.camel@redhat.com> (raw)
In-Reply-To: <20201003131938.9426-2-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 6998 bytes --]
Hi,
seems reasonable to me. Quite simple, but likely good enough as we are
sticking to only use well known names.
Just found a small typo.
Benjamin
On Sat, 2020-10-03 at 15:19 +0200, Hans de Goede wrote:
> On modern systems CPU/GPU/... performance is often dynamically configurable
> in the form of e.g. variable clock-speeds and TPD. The performance is often
> automatically adjusted to the load by some automatic-mechanism (which may
> very well live outside the kernel).
>
> These auto performance-adjustment mechanisms often can be configured with
> one of several performance-profiles, with either a bias towards low-power
> consumption (and cool and quiet) or towards performance (and higher power
> consumption and thermals).
>
> Introduce a new performance_profile class/sysfs API which offers a generic
> API for selecting the performance-profile of these automatic-mechanisms.
>
> Cc: Mark Pearson <markpearson@lenovo.com>
> Cc: Elia Devito <eliadevito@gmail.com>
> Cc: Bastien Nocera <hadess@hadess.net>
> Cc: Benjamin Berg <bberg@redhat.com>
> Cc: linux-pm@vger.kernel.org
> Cc: linux-acpi@vger.kernel.org
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> .../testing/sysfs-class-performance_profile | 104 ++++++++++++++++++
> 1 file changed, 104 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-class-performance_profile
>
> diff --git a/Documentation/ABI/testing/sysfs-class-performance_profile b/Documentation/ABI/testing/sysfs-class-performance_profile
> new file mode 100644
> index 000000000000..9c67cae39600
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-performance_profile
> @@ -0,0 +1,104 @@
> +Performance-profile selection (e.g. /sys/class/performance_profile/thinkpad_acpi/)
> +
> +On modern systems CPU/GPU/... performance is often dynamically configurable
> +in the form of e.g. variable clock-speeds and TPD. The performance is often
> +automatically adjusted to the load by some automatic-mechanism (which may
> +very well live outside the kernel).
> +
> +These auto performance-adjustment mechanisms often can be configured with
> +one of several performance-profiles, with either a bias towards low-power
> +consumption (and cool and quiet) or towards performance (and higher power
> +consumption and thermals).
> +
> +The purpose of the performance_profile class is to offer a generic sysfs
> +API for selecting the performance-profile of these automatic-mechanisms.
> +
> +Note that this API is only for selecting the performance-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 performance-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
Typo, "new" -> "name" I suppose.
> + 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/class/performance_profile/<device>/available_profiles
> +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
> + (and also cool and quiet)
> + balanced-low-power: Balances between low power consumption
> + and performance with a slight bias
> + towards low power
> + balanced: Balance between low power consumption
> + and performance
> + balanced-performance: Balances between performance and low
> + power consumption with a slight bias
> + towards 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/class/performance_profile/<device>/current_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 influencing
> + performance. 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 a
> + 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
> + performance-profiles. In this case writing this file will
> + override the modifications and restore the selected presets.
> +
> +What: /sys/class/performance_profile/<device>/type
> +Date: October 2020
> +Contact: Hans de Goede <hdegoede@redhat.com>
> +Description:
> + Performance-profiles may be system-wide, or for a specific
> + device (e.g. CPU / GPU). System-wide profiles are typically
> + used on devices where where a single cooling solution is
> + shared between all components, such as laptops and NUCs.
> +
> + Reading this file indicates the type of the device for which
> + the thermal-profile is being configured.
> +
> + Valid values: "system"
> + Reserved for future use values: "cpu", "gpu"
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-05 13:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 13:19 [RFC 0/1] Documentation: Add documentation for new performance_profile sysfs class Hans de Goede
2020-10-03 13:19 ` [RFC] " Hans de Goede
2020-10-04 1:33 ` [External] " Mark Pearson
2020-10-04 22:29 ` Elia Devito
2020-10-09 10:52 ` Hans de Goede
2020-10-05 12:58 ` Limonciello, Mario
2020-10-05 14:19 ` Barnabás Pőcze
2020-10-05 16:11 ` Limonciello, Mario
2020-10-05 16:47 ` [External] " Mark Pearson
2020-10-05 16:56 ` Limonciello, Mario
2020-10-05 17:46 ` Mark Pearson
2020-10-07 11:51 ` Bastien Nocera
2020-10-07 15:58 ` Limonciello, Mario
2020-10-07 16:34 ` Bastien Nocera
2020-10-07 18:41 ` Limonciello, Mario
2020-10-12 16:42 ` Rafael J. Wysocki
2020-10-13 13:09 ` Hans de Goede
2020-10-14 13:55 ` Rafael J. Wysocki
2020-10-14 14:16 ` Hans de Goede
2020-10-14 15:46 ` Rafael J. Wysocki
2020-10-14 17:44 ` Elia Devito
2020-10-14 18:11 ` Limonciello, Mario
2020-10-09 11:33 ` Hans de Goede
2020-10-05 13:13 ` Benjamin Berg [this message]
2020-10-09 11:15 ` Hans de Goede
2020-10-03 13:39 ` [RFC 0/1] " Hans de Goede
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=c464996fb3e0e23958c01196fe45f79cafce6cf4.camel@redhat.com \
--to=bberg@redhat.com \
--cc=andy@infradead.org \
--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=markpearson@lenovo.com \
--cc=mgross@linux.intel.com \
--cc=mpearson@lenovo.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;
as well as URLs for NNTP newsgroup(s).