From: "John B. Wyatt IV" <jwyatt@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "Shinji Nomoto (Fujitsu)" <fj5851bi@fujitsu.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>,
John Kacur <jkacur@redhat.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@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: Fri, 20 Jun 2025 13:26:32 -0400 [thread overview]
Message-ID: <aFWZyPs4eBwGcKPu@thinkpad2024> (raw)
In-Reply-To: <0053926a-7b0a-4e49-9acf-fcb1d73134cc@linuxfoundation.org>
On Wed, Jun 18, 2025 at 03:54:56PM -0600, Shuah Khan wrote:
> On 6/3/25 01:16, Shinji Nomoto (Fujitsu) wrote:
> > John Wyatt wrote:
> > > Did you test this on non-x86 systems? If so, would you please provide details on those architectures and systems?
> >
> > Hello,
> >
> > This patch has been tested on Arm-based systems.
> >
> > * It was tested on our internal simulator based on QEMU which supports boost.
> > * It was tested on the Nvidia grace system (which does not support boost).
> > * The cppc_cpufreq driver is working on both of the above systems.
> >
> > We have also confirmed that it continues to work as expected on AMD systems.
> >
>
> John,
>
> Let me know if you are good with this testing details.
I have not tested it, but I the testing details are fine.
--
Sincerely,
John Wyatt
Software Engineer, Core Kernel
Red Hat
next prev parent reply other threads:[~2025-06-20 17:26 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 ` [PATCH 0/2] " John B. Wyatt IV
2025-06-02 22:37 ` 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 [this message]
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=aFWZyPs4eBwGcKPu@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=skhan@linuxfoundation.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