From: shuah <shuah@kernel.org>
To: Abhishek Goel <huntbag@linux.vnet.ibm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: trenn@suse.com, ego@linux.vnet.ibm.com, shuah <shuah@kernel.org>
Subject: Re: [PATCH v2] cpupower : Handle set and info subcommands correctly
Date: Thu, 3 Oct 2019 08:38:53 -0600 [thread overview]
Message-ID: <2614b112-5e19-96dc-179b-8d4e3b8c8858@kernel.org> (raw)
In-Reply-To: <20190913080712.26383-1-huntbag@linux.vnet.ibm.com>
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@ubuntu:~# cpupower info
> System does not support Intel's performance bias setting
>
> root@ubuntu:~# cpupower set -b 10
> Error setting perf-bias value on CPU
>
> With this patch on a non-intel box:
>
> root@ubuntu:~# 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@linux.vnet.ibm.com>
> Acked-by: Thomas Renninger <trenn@suse.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
next prev parent reply other threads:[~2019-10-03 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 8:07 [PATCH v2] cpupower : Handle set and info subcommands correctly Abhishek Goel
2019-10-03 14:38 ` shuah [this message]
2019-10-03 22:15 ` shuah
2019-10-14 9:38 ` Abhishek
2019-10-14 15:02 ` shuah
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=2614b112-5e19-96dc-179b-8d4e3b8c8858@kernel.org \
--to=shuah@kernel.org \
--cc=ego@linux.vnet.ibm.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=trenn@suse.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).