From: Wyes Karny <wyes.karny@amd.com>
To: Huang Rui <ray.huang@amd.com>, "Yuan, Perry" <Perry.Yuan@amd.com>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"Sharma, Deepak" <Deepak.Sharma@amd.com>,
"Fontenot, Nathan" <Nathan.Fontenot@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Huang, Shimmer" <Shimmer.Huang@amd.com>,
"Du, Xiaojian" <Xiaojian.Du@amd.com>,
"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 08/12] cpufreq: amd-pstate: add driver working mode switch support
Date: Wed, 18 Jan 2023 12:04:50 +0530 [thread overview]
Message-ID: <57ce2408-ef8d-c133-4c10-73f226c11c44@amd.com> (raw)
In-Reply-To: <Y8apIMZ3b+dLrpA7@amd.com>
Hi Ray, Perry,
On 1/17/2023 7:26 PM, Huang Rui wrote:
> On Fri, Jan 06, 2023 at 02:14:16PM +0800, Yuan, Perry wrote:
>> From: Perry Yuan <Perry.Yuan@amd.com>
>>
>> While amd-pstate driver was loaded with specific driver mode, it will
>> need to check which mode is enabled for the pstate driver,add this sysfs
>> entry to show the current status
>>
>> $ cat /sys/devices/system/cpu/amd-pstate/status
>> active
>>
>> Meanwhile, user can switch the pstate driver mode with writing mode
>> string to sysfs entry as below.
>>
>> Enable passive mode:
>> $ sudo bash -c "echo passive > /sys/devices/system/cpu/amd-pstate/status"
>>
>> Enable active mode (EPP driver mode):
>> $ sudo bash -c "echo active > /sys/devices/system/cpu/amd-pstate/status"
>>
>> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
>> Signed-off-by: Perry Yuan <Perry.Yuan@amd.com>
>
> Patch is Acked-by: Huang Rui <ray.huang@amd.com>
>
> Wyes, may we have a ack or any comment from you of this patch, as you are
> working on the new guided autonomous mode?
This looks good to me.
Reviewed-by: Wyes Karny <wyes.karny@amd.com>
>
> Thanks,
> Ray
>
>> ---
>> drivers/cpufreq/amd-pstate.c | 118 +++++++++++++++++++++++++++++++++++
>> 1 file changed, 118 insertions(+)
>>
>> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
>> index 2c8b126cec5a..d3f4cdd803f3 100644
>> --- a/drivers/cpufreq/amd-pstate.c
>> +++ b/drivers/cpufreq/amd-pstate.c
>> @@ -63,6 +63,7 @@ static struct cpufreq_driver *current_pstate_driver;
>> static struct cpufreq_driver amd_pstate_driver;
>> static struct cpufreq_driver amd_pstate_epp_driver;
>> static int cppc_state = AMD_PSTATE_DISABLE;
>> +struct kobject *amd_pstate_kobj;
>>
>> static inline int get_mode_idx_from_str(const char *str, size_t size)
>> {
>> @@ -631,6 +632,8 @@ static int amd_pstate_cpu_init(struct cpufreq_policy *policy)
>> policy->driver_data = cpudata;
>>
>> amd_pstate_boost_init(cpudata);
>> + if (!current_pstate_driver->adjust_perf)
>> + current_pstate_driver->adjust_perf = amd_pstate_adjust_perf;
>>
>> return 0;
>>
>> @@ -771,12 +774,99 @@ static ssize_t show_energy_performance_preference(
>> return sysfs_emit(buf, "%s\n", energy_perf_strings[preference]);
>> }
>>
>> +static ssize_t amd_pstate_show_status(char *buf)
>> +{
>> + if (!current_pstate_driver)
>> + return sysfs_emit(buf, "disable\n");
>> +
>> + 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)
>> + 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;
>> + }
>> +
>> + 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;
>> + }
>> +
>> + ret = cpufreq_register_driver(current_pstate_driver);
>> + break;
>> + default:
>> + ret = -EINVAL;
>> + break;
>> + }
>> +
>> + return ret;
>> +}
>> +
>> +static ssize_t show_status(struct kobject *kobj,
>> + struct kobj_attribute *attr, char *buf)
>> +{
>> + ssize_t ret;
>> +
>> + mutex_lock(&amd_pstate_driver_lock);
>> + ret = amd_pstate_show_status(buf);
>> + mutex_unlock(&amd_pstate_driver_lock);
>> +
>> + return ret;
>> +}
>> +
>> +static ssize_t store_status(struct kobject *a, struct kobj_attribute *b,
>> + const char *buf, size_t count)
>> +{
>> + char *p = memchr(buf, '\n', count);
>> + int ret;
>> +
>> + mutex_lock(&amd_pstate_driver_lock);
>> + ret = amd_pstate_update_status(buf, p ? p - buf : count);
>> + mutex_unlock(&amd_pstate_driver_lock);
>> +
>> + return ret < 0 ? ret : count;
>> +}
>> +
>> cpufreq_freq_attr_ro(amd_pstate_max_freq);
>> cpufreq_freq_attr_ro(amd_pstate_lowest_nonlinear_freq);
>>
>> cpufreq_freq_attr_ro(amd_pstate_highest_perf);
>> cpufreq_freq_attr_rw(energy_performance_preference);
>> cpufreq_freq_attr_ro(energy_performance_available_preferences);
>> +define_one_global_rw(status);
>>
>> static struct freq_attr *amd_pstate_attr[] = {
>> &amd_pstate_max_freq,
>> @@ -794,6 +884,15 @@ static struct freq_attr *amd_pstate_epp_attr[] = {
>> NULL,
>> };
>>
>> +static struct attribute *pstate_global_attributes[] = {
>> + &status.attr,
>> + NULL
>> +};
>> +
>> +static const struct attribute_group amd_pstate_global_attr_group = {
>> + .attrs = pstate_global_attributes,
>> +};
>> +
>> static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
>> {
>> int min_freq, max_freq, nominal_freq, lowest_nonlinear_freq, ret;
>> @@ -1153,6 +1252,25 @@ static int __init amd_pstate_init(void)
>> if (ret)
>> pr_err("failed to register with return %d\n", ret);
>>
>> + amd_pstate_kobj = kobject_create_and_add("amd_pstate", &cpu_subsys.dev_root->kobj);
>> + if (!amd_pstate_kobj) {
>> + ret = -EINVAL;
>> + pr_err("global sysfs registration failed.\n");
>> + goto kobject_free;
>> + }
>> +
>> + ret = sysfs_create_group(amd_pstate_kobj, &amd_pstate_global_attr_group);
>> + if (ret) {
>> + pr_err("sysfs attribute export failed with error %d.\n", ret);
>> + goto global_attr_free;
>> + }
>> +
>> + return ret;
>> +
>> +global_attr_free:
>> + kobject_put(amd_pstate_kobj);
>> +kobject_free:
>> + cpufreq_unregister_driver(current_pstate_driver);
>> return ret;
>> }
>> device_initcall(amd_pstate_init);
>> --
>> 2.34.1
>>
--
Thanks & Regards,
Wyes
next prev parent reply other threads:[~2023-01-18 7:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 6:14 [PATCH v10 00/12] Implement AMD Pstate EPP Driver Perry Yuan
2023-01-06 6:14 ` [PATCH v10 01/12] ACPI: CPPC: Add AMD pstate energy performance preference cppc control Perry Yuan
2023-01-17 11:10 ` Huang Rui
2023-01-06 6:14 ` [PATCH v10 02/12] Documentation: amd-pstate: add EPP profiles introduction Perry Yuan
2023-01-17 11:45 ` Huang Rui
2023-01-06 6:14 ` [PATCH v10 03/12] cpufreq: intel_pstate: use common macro definition for Energy Preference Performance(EPP) Perry Yuan
2023-01-06 9:38 ` kernel test robot
2023-01-06 10:19 ` kernel test robot
2023-01-06 6:14 ` [PATCH v10 04/12] cpufreq: amd-pstate: optimize driver working mode selection in amd_pstate_param() Perry Yuan
2023-01-17 11:57 ` Huang Rui
2023-01-06 6:14 ` [PATCH v10 05/12] cpufreq: amd-pstate: implement Pstate EPP support for the AMD processors Perry Yuan
2023-01-06 11:19 ` Wyes Karny
2023-01-10 15:21 ` Yuan, Perry
2023-01-10 18:15 ` kernel test robot
2023-01-17 13:34 ` Huang Rui
2023-01-06 6:14 ` [PATCH v10 06/12] cpufreq: amd-pstate: implement amd pstate cpu online and offline callback Perry Yuan
2023-01-06 6:14 ` [PATCH v10 07/12] cpufreq: amd-pstate: implement suspend and resume callbacks Perry Yuan
2023-01-06 6:14 ` [PATCH v10 08/12] cpufreq: amd-pstate: add driver working mode switch support Perry Yuan
2023-01-17 13:56 ` Huang Rui
2023-01-18 6:34 ` Wyes Karny [this message]
2023-01-18 7:27 ` Yuan, Perry
2023-01-06 6:14 ` [PATCH v10 09/12] Documentation: amd-pstate: add amd pstate driver mode introduction Perry Yuan
2023-01-06 6:14 ` [PATCH v10 10/12] Documentation: introduce amd pstate active mode kernel command line options Perry Yuan
2023-01-06 6:14 ` [PATCH v10 11/12] cpufreq: amd-pstate: convert sprintf with sysfs_emit() Perry Yuan
2023-01-06 6:14 ` [PATCH v10 12/12] Documentation: amd-pstate: introduce new global sysfs attributes Perry Yuan
2023-01-17 14:11 ` Huang Rui
2023-01-10 18:00 ` [PATCH v10 00/12] Implement AMD Pstate EPP Driver Wyes Karny
2023-01-17 14:03 ` Huang Rui
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=57ce2408-ef8d-c133-4c10-73f226c11c44@amd.com \
--to=wyes.karny@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Deepak.Sharma@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Nathan.Fontenot@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Shimmer.Huang@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=ray.huang@amd.com \
--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
all inboxes | Powered by JetHome®