From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Shinji Nomoto <fj5851bi@fujitsu.com>
Cc: Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
John Kacur <jkacur@redhat.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] cpupower: Allow control of boost feature on non-x86 based systems with boost support.
Date: Thu, 29 May 2025 07:48:05 -0400 [thread overview]
Message-ID: <aDhJdTWzDihchywc@thinkpad2024> (raw)
In-Reply-To: <20250522061122.2149188-1-fj5851bi@fujitsu.com>
Hello Shinji, ty for your patch.
On Thu, May 22, 2025 at 03:10:57PM +0900, Shinji Nomoto wrote:
> The cpufreq subsystem has a generic sysfs interface for controlling boost
> (/sys/devices/system/cpu/cpufreq/boost).
> The sysfs interface can be used to enable boost control from the cpupower
> command on non-x86 platforms as well. So, allow boost controlling on
> non-x86 system if boost sysfs file exists.
Did you test this on non-x86 systems? If so, would you please provide
details on those architectures and systems?
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
next prev parent reply other threads:[~2025-05-29 11:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:10 [PATCH 0/2] cpupower: Allow control of boost feature on non-x86 based systems with boost support Shinji Nomoto
2025-05-22 6:10 ` [PATCH 1/2] cpupower: Fix a bug where the -t option of the set subcommand was not working Shinji Nomoto
2025-05-22 6:10 ` [PATCH 2/2] cpupower: Allow control of boost feature on non-x86 based systems with boost support Shinji Nomoto
2025-05-29 11:48 ` John B. Wyatt IV [this message]
2025-06-02 22:37 ` [PATCH 0/2] " Shuah Khan
2025-06-03 7:16 ` Shinji Nomoto (Fujitsu)
2025-06-18 21:54 ` Shuah Khan
2025-06-20 17:26 ` John B. Wyatt IV
2025-07-22 7:30 ` Shinji Nomoto (Fujitsu)
2025-07-22 17:59 ` John B. Wyatt IV
2025-07-24 18:21 ` Shuah Khan
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=aDhJdTWzDihchywc@thinkpad2024 \
--to=jwyatt@redhat.com \
--cc=fj5851bi@fujitsu.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@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).