lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87plsavoup.fsf@BLR-5CG11610CF.amd.com>
Date: Fri, 21 Jun 2024 11:06:46 +0530
From: Gautham R.Shenoy <gautham.shenoy@....com>
To: Mario Limonciello <mario.limonciello@....com>, Perry Yuan
	<perry.yuan@....com>, <rafael.j.wysocki@...el.com>, <viresh.kumar@...aro.org>
CC: <Xinmei.Huang@....com>, <Xiaojian.Du@....com>, <Li.Meng@....com>,
	<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v12 5/9] cpufreq: amd-pstate: implement cpb_boost sysfs
 entry for boost control

Mario Limonciello <mario.limonciello@....com> writes:

> On 6/19/2024 04:16, Perry Yuan wrote:
>> From: Perry Yuan <Perry.Yuan@....com>
>> 
>> With this new sysfs entry `cpb_boost`created, user can change CPU boost
>> state dynamically under `active`, `guided` and `passive` modes.
>> And the highest perf and frequency will also be updated as the boost
>> state changing.
>
> s/changing/changes/
>
>> 
>> 0): check current boost state
>> cat /sys/devices/system/cpu/amd_pstate/cpb_boost
>> 
>> 1): disable CPU boost
>> sudo bash -c "echo 0 > /sys/devices/system/cpu/amd_pstate/cpb_boost"
>> 
>> 2): enable CPU boost
>> sudo bash -c "echo 1 > /sys/devices/system/cpu/amd_pstate/cpb_boost"

>From the point of view of the functionality this new interface is no
different from

/sys/devices/system/cpu/cpufreq/boost, which is currently suppported for
the passive mode and the guided mode.

Is there anything that prevents us from enabling this interface for the
active mode as well? 

It is easier if we use the common interface because tools such as
cpupower will then not need to fiddle with several different sysfs files
to enable/disable boost.

--
Thanks and Regards
gautham.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ