public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tor Vic <torvic9@mailbox.org>
To: Meng Li <li.meng@amd.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Huang Rui <ray.huang@amd.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, linux-acpi@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-kselftest@vger.kernel.org,
	Nathan Fontenot <nathan.fontenot@amd.com>,
	Deepak Sharma <deepak.sharma@amd.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Shimmer Huang <shimmer.huang@amd.com>,
	Perry Yuan <Perry.Yuan@amd.com>,
	Xiaojian Du <Xiaojian.Du@amd.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Borislav Petkov <bp@alien8.de>,
	Oleksandr Natalenko <oleksandr@natalenko.name>
Subject: Re: [PATCH V11 0/7] amd-pstate preferred core
Date: Thu, 30 Nov 2023 15:35:20 +0100	[thread overview]
Message-ID: <09ea3d40-e8f6-4cba-a576-ffeda8c02734@mailbox.org> (raw)
In-Reply-To: <20231129065437.290183-1-li.meng@amd.com>



On 11/29/23 07:54, Meng Li wrote:
> Hi all:
> 
> The core frequency is subjected to the process variation in semiconductors.
> Not all cores are able to reach the maximum frequency respecting the
> infrastructure limits. Consequently, AMD has redefined the concept of
> maximum frequency of a part. This means that a fraction of cores can reach
> maximum frequency. To find the best process scheduling policy for a given
> scenario, OS needs to know the core ordering informed by the platform through
> highest performance capability register of the CPPC interface.
> 
> Earlier implementations of amd-pstate preferred core only support a static
> core ranking and targeted performance. Now it has the ability to dynamically
> change the preferred core based on the workload and platform conditions and
> accounting for thermals and aging.
> 
> Amd-pstate driver utilizes the functions and data structures provided by
> the ITMT architecture to enable the scheduler to favor scheduling on cores
> which can be get a higher frequency with lower voltage.
> We call it amd-pstate preferred core.
> 
> Here sched_set_itmt_core_prio() is called to set priorities and
> sched_set_itmt_support() is called to enable ITMT feature.
> Amd-pstate driver uses the highest performance value to indicate
> the priority of CPU. The higher value has a higher priority.
> 
> Amd-pstate driver will provide an initial core ordering at boot time.
> It relies on the CPPC interface to communicate the core ranking to the
> operating system and scheduler to make sure that OS is choosing the cores
> with highest performance firstly for scheduling the process. When amd-pstate
> driver receives a message with the highest performance change, it will
> update the core ranking.
> 
> Changes from V10->V11:
> - cpufreq: amd-pstate:
> - - according Perry's commnts, I replace the string with str_enabled_disable().
> 

Hi,

Using clang-17, I get the following warning:

----
   drivers/cpufreq/amd-pstate.c:793:34: warning: variable 'cpudata' is 
uninitialized when used here [-Wuninitialized]
     793 |         if ((!amd_pstate_prefcore) || (!cpudata->hw_prefcore))
         |                                         ^~~~~~~
   drivers/cpufreq/amd-pstate.c:789:29: note: initialize the variable 
'cpudata' to silence this warning
     789 |         struct amd_cpudata *cpudata;
         |                                    ^
         |                                     = NULL
   1 warning generated.
----

Cheers,
Tor

      parent reply	other threads:[~2023-11-30 14:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  6:54 [PATCH V11 0/7] amd-pstate preferred core Meng Li
2023-11-29  6:54 ` [PATCH V11 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion Meng Li
2023-11-30  6:00   ` Yuan, Perry
2023-11-29  6:54 ` [PATCH V11 2/7] acpi: cppc: Add get the highest performance cppc control Meng Li
2023-11-30  6:02   ` Yuan, Perry
2023-11-29  6:54 ` [PATCH V11 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting Meng Li
2023-11-29  6:54 ` [PATCH V11 4/7] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-11-30  6:04   ` Yuan, Perry
2023-11-29  6:54 ` [PATCH V11 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically Meng Li
2023-11-30  5:49   ` Yuan, Perry
2023-11-29  6:54 ` [PATCH V11 6/7] Documentation: amd-pstate: introduce amd-pstate preferred core Meng Li
2023-11-30  5:51   ` Yuan, Perry
2023-11-29  6:54 ` [PATCH V11 7/7] Documentation: introduce amd-pstate preferrd core mode kernel command line options Meng Li
2023-11-30  5:52   ` Yuan, Perry
2023-11-30 14:35 ` Tor Vic [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=09ea3d40-e8f6-4cba-a576-ffeda8c02734@mailbox.org \
    --to=torvic9@mailbox.org \
    --cc=Perry.Yuan@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=bp@alien8.de \
    --cc=deepak.sharma@amd.com \
    --cc=li.meng@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=nathan.fontenot@amd.com \
    --cc=oleksandr@natalenko.name \
    --cc=rafael.j.wysocki@intel.com \
    --cc=ray.huang@amd.com \
    --cc=shimmer.huang@amd.com \
    --cc=skhan@linuxfoundation.org \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@kernel.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