From: Huang Rui <ray.huang@amd.com>
To: "Yuan, Perry" <Perry.Yuan@amd.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Fontenot, Nathan" <Nathan.Fontenot@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Sharma, Deepak" <Deepak.Sharma@amd.com>,
"Huang, Shimmer" <Shimmer.Huang@amd.com>,
"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
"Du, Xiaojian" <Xiaojian.Du@amd.com>,
"Karny, Wyes" <Wyes.Karny@amd.com>,
"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
"Narayan, Ananth" <Ananth.Narayan@amd.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/5] AMD Pstate driver Urgent Change
Date: Thu, 17 Nov 2022 13:35:32 +0800 [thread overview]
Message-ID: <Y3XIJLgIR0aXt3hO@amd.com> (raw)
In-Reply-To: <20221117024955.3319484-1-Perry.Yuan@amd.com>
On Thu, Nov 17, 2022 at 10:49:50AM +0800, Yuan, Perry wrote:
> The patchset changed amd-pstate driver as built-in type to resolve the
> driver loading sequence problem, otherwise the acpi-cpufreq driver will
> be loaded as the default cpufreq scaling driver instead of amd-pstate.
>
> Some new kernel parameters are added to allow user to disable pstate driver
> and load driver with passive mode which use governors to do the
> frequency scaling control.
>
> * `amd_pstate=disabled` or no parameters will not load pstate driver.
> * `amd_pstate=passive` will load pstate driver with passive mode.
>
> Set the `amd_pstate` driver disabled by default because of performance
> degradation on a number of AMD ASICs in the passive mode driver,
> especially the shared memory support processors.
>
> EPP support for the amd_pstate driver is under review. With EPP support,
> the said performance issue is resolved. Once that gets upstream,
> the `active` mode amd_pstate_epp driver may be enabled by default.
>
> Perry Yuan (4):
> cpufreq: amd-pstate: change amd-pstate driver to be built-in type
> cpufreq: amd-pstate: add amd-pstate driver parameter for mode
> selection
> Documentation: amd-pstate: add driver working mode introduction
> Documentation: add amd-pstate kernel command line options
>
> Wyes Karny (1):
> cpufreq: amd-pstate: cpufreq: amd-pstate: reset MSR_AMD_PERF_CTL
> register at init
Series are Acked-by: Huang Rui <ray.huang@amd.com>
Hi Rafeal,
These series are the fixes for our new processors. Would you mind to merge
them into pm-6.1-rc6 or pm-6.1-rc7?
Thanks,
Ray
prev parent reply other threads:[~2022-11-17 5:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 2:49 [PATCH 0/5] AMD Pstate driver Urgent Change Perry Yuan
2022-11-17 2:49 ` [PATCH 1/5] cpufreq: amd-pstate: cpufreq: amd-pstate: reset MSR_AMD_PERF_CTL register at init Perry Yuan
2022-11-17 4:08 ` Gautham R. Shenoy
2022-11-17 5:03 ` Wyes Karny
2022-11-17 2:49 ` [PATCH 2/5] cpufreq: amd-pstate: change amd-pstate driver to be built-in type Perry Yuan
2022-11-17 4:09 ` Gautham R. Shenoy
2022-11-17 5:04 ` Wyes Karny
2022-11-17 2:49 ` [PATCH 3/5] cpufreq: amd-pstate: add amd-pstate driver parameter for mode selection Perry Yuan
2022-11-17 4:13 ` Gautham R. Shenoy
2022-11-17 5:06 ` Wyes Karny
2022-11-17 2:49 ` [PATCH 4/5] Documentation: amd-pstate: add driver working mode introduction Perry Yuan
2022-11-17 4:15 ` Gautham R. Shenoy
2022-11-17 4:17 ` Yuan, Perry
2022-11-17 5:06 ` Wyes Karny
2022-11-17 2:49 ` [PATCH 5/5] Documentation: add amd-pstate kernel command line options Perry Yuan
2022-11-17 4:16 ` Gautham R. Shenoy
2022-11-17 5:08 ` Wyes Karny
2022-11-17 5:35 ` Huang Rui [this message]
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=Y3XIJLgIR0aXt3hO@amd.com \
--to=ray.huang@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Ananth.Narayan@amd.com \
--cc=Deepak.Sharma@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Nathan.Fontenot@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Shimmer.Huang@amd.com \
--cc=Wyes.Karny@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
/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