From: 徐福海 <xufuhai1992@gmail.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
shuah@kernel.org, Thomas Renninger <trenn@suse.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
lishujin@kuaishou.com, xufuhai <xufuhai@kuaishou.com>
Subject: Re: [PATCH 1/2] cpupower: Fix amd cpu (family < 0x17) active state issue
Date: Sun, 25 Apr 2021 10:41:40 +0800 [thread overview]
Message-ID: <a7418aab-847f-3c06-ddc4-3c6aaea90b7c@gmail.com> (raw)
In-Reply-To: <87e43451-e7d3-877e-7081-92838ae699e6@linuxfoundation.org>
okay, I believe the two patches are for fixing defferent issue, I will update my patches as your mention
THANKS
在 2021/4/24 上午6:26, Shuah Khan 写道:
> On 4/19/21 8:27 PM, 徐福海 wrote:
>> From: xufuhai<xufuhai@kuaishou.com>
>>
>> For the old AMD processor (family < 0x17), cpupower will call the
>> amd_pci_get_num_boost_states function, but for the non-root user
>> pci_read_byte function (implementation comes from the psutil library),
>> val will be set to 0xff, indicating that there is no read function
>> callback. At this time, the original logic will set the cpupower turbo
>> active state to yes. This is an obvious issue~
>>
>> Reproduce procedure:
>> cpupower frequency-info
>>
>> Reported-by: yangrui<yangrui@kuaishou.com>
>> Signed-off-by: xufuhai<xufuhai@kuaishou.com>
>
> Also your Signed-off-by should match the from address.
> There is a mismatch between the two.
>
>> Signed-off-by: chenguanqiao<chenguanqiao@kuaishou.com>
>> Signed-off-by: lishujin<lishujin@kuaishou.com>
>> Reviewed-by: Thomas Renninger<trenn@suse.com>
>> ---
>> tools/power/cpupower/utils/helpers/amd.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/tools/power/cpupower/utils/helpers/amd.c b/tools/power/cpupower/utils/helpers/amd.c
>> index 97f2c857048e..6f9504906afa 100644
>> --- a/tools/power/cpupower/utils/helpers/amd.c
>> +++ b/tools/power/cpupower/utils/helpers/amd.c
>> @@ -137,6 +137,13 @@ int amd_pci_get_num_boost_states(int *active, int *states)
>> return -ENODEV;
>> val = pci_read_byte(device, 0x15c);
>> +
>> + /* If val is 0xff, meaning has no permisson to
>> + * get the boost states, return -1
>> + */
>> + if (val == 0xff)
>> + return -1;
>> +
>> if (val & 3)
>> *active = 1;
>> else
>> --
>> 2.24.3 (Apple Git-128)
>>
>
> I am seeing two patches with the same commit summary,
> should these two be a singles patch?
>
> https://patchwork.kernel.org/project/linux-pm/patch/6e35df20-753a-6c9c-8786-3fc87cdd17ba@gmail.com/
>
> Please combine the two and send single patch if they fix the
> same problem. If not, please change the commit log to reflect
> the difference.
>
> thanks,
> -- Shuah
>
>
next prev parent reply other threads:[~2021-04-25 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bf312780-dda7-d08f-6098-1d8a7d4044e4@gmail.com>
[not found] ` <378e58d3-5300-1179-44bb-bc2b42a3beb0@gmail.com>
2021-04-23 22:26 ` [PATCH 1/2] cpupower: Fix amd cpu (family < 0x17) active state issue Shuah Khan
2021-04-25 2:41 ` 徐福海 [this message]
[not found] <20210324082838.41462-1-xufuhai1992@gmail.com>
2021-03-29 11:10 ` [PATCH 1/2] cpupower: fix " Thomas Renninger
2021-03-30 3:47 ` xufuhai
2021-04-08 2:22 ` xufuhai
2021-03-24 10:27 xufuhai
2021-03-26 20:13 ` Shuah Khan
2021-03-29 3:51 ` xufuhai
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=a7418aab-847f-3c06-ddc4-3c6aaea90b7c@gmail.com \
--to=xufuhai1992@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lishujin@kuaishou.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=trenn@suse.com \
--cc=xufuhai@kuaishou.com \
/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).