[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2614b112-5e19-96dc-179b-8d4e3b8c8858@kernel.org>
Date: Thu, 3 Oct 2019 08:38:53 -0600
From: shuah <shuah@...nel.org>
To: Abhishek Goel <huntbag@...ux.vnet.ibm.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: trenn@...e.com, ego@...ux.vnet.ibm.com, shuah <shuah@...nel.org>
Subject: Re: [PATCH v2] cpupower : Handle set and info subcommands correctly
On 9/13/19 2:07 AM, Abhishek Goel wrote:
> Cpupower tool has set and info options which are being used only by
> x86 machines. This patch removes support for these two subcommands
> from generic cpupower utility. Thus, these two subcommands will now be
> available only for intel.
> This removes the ambiguous error message while using set option in case
> of using non-intel systems.
>
> Without this patch on a non-intel box:
>
> root@...ntu:~# cpupower info
> System does not support Intel's performance bias setting
>
> root@...ntu:~# cpupower set -b 10
> Error setting perf-bias value on CPU
>
> With this patch on a non-intel box:
>
> root@...ntu:~# cpupower info
> Supported commands are:
> frequency-info
> frequency-set
> idle-info
> idle-set
> monitor
> help
>
> Same result for set subcommand.
>
> This patch does not affect results on a intel box.
>
> Signed-off-by: Abhishek Goel <huntbag@...ux.vnet.ibm.com>
> Acked-by: Thomas Renninger <trenn@...e.de>
> ---
>
> changes from v1:
> Instead of bailing out early in set and info commands, in V2, we
> are cutting out support for these two commands for non-intel
> systems.
thanks. I will get this in for 5.4-rc3 veru likely. Definitely in 5.4
-- Shuah
Powered by blists - more mailing lists