From: Wyes Karny <wyes.karny@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Rafael J Wysocki <rafael@kernel.org>,
Huang Rui <ray.huang@amd.com>, Jonathan Corbet <corbet@lwn.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
Perry.Yuan@amd.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
santosh.shukla@amd.com, Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
Borislav Petkov <bp@alien8.de>,
Ananth Narayan <ananth.narayan@amd.com>,
gautham.shenoy@amd.com, Tor Vic <torvic9@mailbox.org>
Subject: Re: [PATCH v4 5/6] cpufreq: amd_pstate: Add guided mode control support via sysfs
Date: Tue, 31 Jan 2023 17:48:51 +0000 [thread overview]
Message-ID: <Y9lUgxevhdlv840K@beas> (raw)
In-Reply-To: <661a55c4-5703-ef84-728a-229997737416@amd.com>
On 31 Jan 07:45, Mario Limonciello wrote:
> On 1/30/23 23:21, Wyes Karny wrote:
> > amd_pstate driver's `status` sysfs entry helps to control the driver's
> > mode dynamically by user. After the addition of guided mode the
> > combinations of mode transitions have been increased (16 combinations).
> > Therefore optimise the amd_pstate_update_status function by implementing
> > a state transition table.
> >
> > There are 4 states amd_pstate supports, namely: 'disable', 'passive',
> > 'active', and 'guided'. The transition from any state to any other
> > state is possible after this change. Only if the state requested matches
> > with the current state then -EBUSY value is returned.
>
> I realized this after I finished reviewing doc patch, but you probably want
> to explain -EBUSY return code in documentation patch too.
Yes, I'll add this to documentation. Thanks!
>
> >
> > Sysfs interface:
> >
> > To disable amd_pstate driver:
> > # echo disable > /sys/devices/system/cpu/amd_pstate/status
> >
> > To enable passive mode:
> > # echo passive > /sys/devices/system/cpu/amd_pstate/status
> >
> > To change mode to active:
> > # echo active > /sys/devices/system/cpu/amd_pstate/status
> >
> > To change mode to guided:
> > # echo guided > /sys/devices/system/cpu/amd_pstate/status
> >
> > Signed-off-by: Wyes Karny <wyes.karny@amd.com>
> > ---
> > drivers/cpufreq/amd-pstate.c | 150 +++++++++++++++++++++++++----------
> > 1 file changed, 108 insertions(+), 42 deletions(-)
> >
> > diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> > index 48ab4684c3a5..6c522dec6967 100644
> > --- a/drivers/cpufreq/amd-pstate.c
> > +++ b/drivers/cpufreq/amd-pstate.c
> > @@ -65,6 +65,8 @@ static struct cpufreq_driver amd_pstate_epp_driver;
> > static int cppc_state = AMD_PSTATE_DISABLE;
> > struct kobject *amd_pstate_kobj;
> > +typedef int (*cppc_mode_transition_fn)(int);
> > +
> > static inline int get_mode_idx_from_str(const char *str, size_t size)
> > {
> > int i;
> > @@ -797,6 +799,105 @@ static ssize_t show_energy_performance_preference(
> > return sysfs_emit(buf, "%s\n", energy_perf_strings[preference]);
> > }
> > +static void amd_pstate_driver_cleanup(void)
> > +{
> > + amd_pstate_enable(false);
> > + cppc_state = AMD_PSTATE_DISABLE;
> > + current_pstate_driver = NULL;
> > +}
> > +
> > +static int amd_pstate_register_driver(int mode)
> > +{
> > + int ret;
> > +
> > + if (mode == AMD_PSTATE_PASSIVE || mode == AMD_PSTATE_GUIDED)
> > + current_pstate_driver = &amd_pstate_driver;
> > + else if (mode == AMD_PSTATE_ACTIVE)
> > + current_pstate_driver = &amd_pstate_epp_driver;
> > + else
> > + return -EINVAL;
> > +
> > + cppc_state = mode;
> > + ret = cpufreq_register_driver(current_pstate_driver);
> > + if (ret) {
> > + amd_pstate_driver_cleanup();
> > + return ret;
> > + }
> > + return 0;
> > +}
> > +
> > +static int amd_pstate_unregister_driver(int dummy)
> > +{
> > + int ret;
> > +
> > + ret = cpufreq_unregister_driver(current_pstate_driver);
> > +
> > + if (ret)
> > + return ret;
> > +
> > + amd_pstate_driver_cleanup();
> > + return 0;
> > +}
> > +
> > +static int amd_pstate_change_mode_without_dvr_change(int mode)
> > +{
> > + int cpu = 0;
> > +
> > + cppc_state = mode;
> > +
> > + if (boot_cpu_has(X86_FEATURE_CPPC) || cppc_state == AMD_PSTATE_ACTIVE)
> > + return 0;
> > +
> > + for_each_present_cpu(cpu) {
> > + cppc_set_auto_sel(cpu, (cppc_state == AMD_PSTATE_PASSIVE) ? 0 : 1);
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +static int amd_pstate_change_driver_mode(int mode)
> > +{
> > + int ret;
> > +
> > + ret = amd_pstate_unregister_driver(0);
> > + if (ret)
> > + return ret;
> > +
> > + ret = amd_pstate_register_driver(mode);
> > + if (ret)
> > + return ret;
> > +
> > + return 0;
> > +}
> > +
> > +/* Mode transition table */
>
> This seems to be a pointless comment to me.
>
> > +cppc_mode_transition_fn mode_state_machine[AMD_PSTATE_MAX][AMD_PSTATE_MAX] = {
> > + [AMD_PSTATE_DISABLE] = {
> > + [AMD_PSTATE_DISABLE] = NULL,
> > + [AMD_PSTATE_PASSIVE] = amd_pstate_register_driver,
> > + [AMD_PSTATE_ACTIVE] = amd_pstate_register_driver,
> > + [AMD_PSTATE_GUIDED] = amd_pstate_register_driver,
> > + },
> > + [AMD_PSTATE_PASSIVE] = {
> > + [AMD_PSTATE_DISABLE] = amd_pstate_unregister_driver,
> > + [AMD_PSTATE_PASSIVE] = NULL,
> > + [AMD_PSTATE_ACTIVE] = amd_pstate_change_driver_mode,
> > + [AMD_PSTATE_GUIDED] = amd_pstate_change_mode_without_dvr_change,
> > + },
> > + [AMD_PSTATE_ACTIVE] = {
> > + [AMD_PSTATE_DISABLE] = amd_pstate_unregister_driver,
> > + [AMD_PSTATE_PASSIVE] = amd_pstate_change_driver_mode,
> > + [AMD_PSTATE_ACTIVE] = NULL,
> > + [AMD_PSTATE_GUIDED] = amd_pstate_change_driver_mode,
> > + },
> > + [AMD_PSTATE_GUIDED] = {
> > + [AMD_PSTATE_DISABLE] = amd_pstate_unregister_driver,
> > + [AMD_PSTATE_PASSIVE] = amd_pstate_change_mode_without_dvr_change,
> > + [AMD_PSTATE_ACTIVE] = amd_pstate_change_driver_mode,
> > + [AMD_PSTATE_GUIDED] = NULL,
> > + },
> > +};
> > +
> > static ssize_t amd_pstate_show_status(char *buf)
> > {
> > if (!current_pstate_driver)
> > @@ -805,57 +906,22 @@ static ssize_t amd_pstate_show_status(char *buf)
> > return sysfs_emit(buf, "%s\n", amd_pstate_mode_string[cppc_state]);
> > }
> > -static void amd_pstate_driver_cleanup(void)
> > -{
> > - current_pstate_driver = NULL;
> > -}
> > -
> > static int amd_pstate_update_status(const char *buf, size_t size)
> > {
> > - int ret;
> > int mode_idx;
> > - if (size > 7 || size < 6)
> > + if (size > strlen("passive") || size < strlen("active"))
> > return -EINVAL;
> > - mode_idx = get_mode_idx_from_str(buf, size);
> > - switch(mode_idx) {
> > - case AMD_PSTATE_DISABLE:
> > - if (!current_pstate_driver)
> > - return -EINVAL;
> > - if (cppc_state == AMD_PSTATE_ACTIVE)
> > - return -EBUSY;
> > - ret = cpufreq_unregister_driver(current_pstate_driver);
> > - amd_pstate_driver_cleanup();
> > - break;
> > - case AMD_PSTATE_PASSIVE:
> > - if (current_pstate_driver) {
> > - if (current_pstate_driver == &amd_pstate_driver)
> > - return 0;
> > - cpufreq_unregister_driver(current_pstate_driver);
> > - cppc_state = AMD_PSTATE_PASSIVE;
> > - current_pstate_driver = &amd_pstate_driver;
> > - }
> > + mode_idx = get_mode_idx_from_str(buf, size);
> > - ret = cpufreq_register_driver(current_pstate_driver);
> > - break;
> > - case AMD_PSTATE_ACTIVE:
> > - if (current_pstate_driver) {
> > - if (current_pstate_driver == &amd_pstate_epp_driver)
> > - return 0;
> > - cpufreq_unregister_driver(current_pstate_driver);
> > - current_pstate_driver = &amd_pstate_epp_driver;
> > - cppc_state = AMD_PSTATE_ACTIVE;
> > - }
> > + if (mode_idx < 0 || mode_idx >= AMD_PSTATE_MAX)
> > + return -EINVAL;
> > - ret = cpufreq_register_driver(current_pstate_driver);
> > - break;
> > - default:
> > - ret = -EINVAL;
> > - break;
> > - }
> > + if (mode_state_machine[cppc_state][mode_idx])
> > + return mode_state_machine[cppc_state][mode_idx](mode_idx);
> > - return ret;
> > + return -EBUSY;
> > }
> > static ssize_t show_status(struct kobject *kobj,
>
> With one nit fixed,
>
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
next prev parent reply other threads:[~2023-01-31 17:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 5:21 [PATCH v4 0/6] amd_pstate: Add guided autonomous mode support Wyes Karny
2023-01-31 5:21 ` [PATCH v4 1/6] acpi: cppc: Add min and max perf reg writing support Wyes Karny
2023-01-31 5:21 ` [PATCH v4 2/6] acpi: cppc: Add auto select register read/write support Wyes Karny
2023-01-31 5:21 ` [PATCH v4 3/6] cpufreq: amd_pstate: Add guided autonomous mode Wyes Karny
2023-01-31 13:37 ` Mario Limonciello
2023-01-31 17:45 ` Wyes Karny
2023-01-31 5:21 ` [PATCH v4 4/6] Documentation: amd_pstate: Move amd_pstate param to alphabetical order Wyes Karny
2023-01-31 5:21 ` [PATCH v4 5/6] cpufreq: amd_pstate: Add guided mode control support via sysfs Wyes Karny
2023-01-31 13:45 ` Mario Limonciello
2023-01-31 17:48 ` Wyes Karny [this message]
2023-02-02 7:41 ` Russell Haley
2023-02-03 8:36 ` Wyes Karny
2023-01-31 5:21 ` [PATCH v4 6/6] Documentation: amd_pstate: Update amd_pstate status sysfs for guided Wyes Karny
2023-01-31 12:42 ` Bagas Sanjaya
2023-01-31 13:12 ` Mario Limonciello
2023-01-31 10:37 ` [PATCH v4 0/6] amd_pstate: Add guided autonomous mode support torvic9
2023-01-31 15:13 ` Oleksandr Natalenko
2023-01-31 16:12 ` torvic9
2023-01-31 17:50 ` Wyes Karny
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=Y9lUgxevhdlv840K@beas \
--to=wyes.karny@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=ananth.narayan@amd.com \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gautham.shenoy@amd.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=robert.moore@intel.com \
--cc=santosh.shukla@amd.com \
--cc=torvic9@mailbox.org \
--cc=viresh.kumar@linaro.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).