From: Peter Zijlstra <peterz@infradead.org>
To: Meng Li <li.meng@amd.com>
Cc: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Huang Rui <ray.huang@amd.com>,
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>
Subject: Re: [PATCH V8 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting.
Date: Tue, 10 Oct 2023 12:36:29 +0200 [thread overview]
Message-ID: <20231010103629.GI377@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20231009024932.2563622-4-li.meng@amd.com>
On Mon, Oct 09, 2023 at 10:49:28AM +0800, Meng Li wrote:
> +static void amd_pstate_init_prefcore(struct amd_cpudata *cpudata)
> +{
> + int ret;
> + u32 highest_perf;
> + static u32 max_highest_perf = 0, min_highest_perf = U32_MAX;
> +
> + ret = amd_pstate_get_highest_perf(cpudata->cpu, &highest_perf);
> + if (ret)
> + return;
> +
> + cpudata->hw_prefcore = true;
> + /* check if CPPC preferred core feature is enabled*/
> + if (highest_perf == AMD_PSTATE_MAX_CPPC_PERF) {
> + pr_debug("AMD CPPC preferred core is unsupported!\n");
> + cpudata->hw_prefcore = false;
> + return;
> + }
> +
> + if (!amd_pstate_prefcore)
> + return;
> +
> + /*
> + * The priorities can be set regardless of whether or not
> + * sched_set_itmt_support(true) has been called and it is valid to
> + * update them at any time after it has been called.
> + */
> + sched_set_itmt_core_prio(highest_perf, cpudata->cpu);
You still got the whole u32 vs int thing confused, I've only pointed
that out *TWICE* before.
Boris, can you pull out the clue hammer please?
> +
> + if (max_highest_perf <= min_highest_perf) {
> + if (highest_perf > max_highest_perf)
> + max_highest_perf = highest_perf;
> +
> + if (highest_perf < min_highest_perf)
> + min_highest_perf = highest_perf;
> +
> + if (max_highest_perf > min_highest_perf) {
> + /*
> + * This code can be run during CPU online under the
> + * CPU hotplug locks, so sched_set_itmt_support()
> + * cannot be called from here. Queue up a work item
> + * to invoke it.
> + */
> + schedule_work(&sched_prefcore_work);
> + }
> + }
> +}
next prev parent reply other threads:[~2023-10-10 10:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 2:49 [PATCH V8 0/7] amd-pstate preferred core Meng Li
2023-10-09 2:49 ` [PATCH V8 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion Meng Li
2023-10-09 6:19 ` Wyes Karny
2023-10-10 10:30 ` Peter Zijlstra
2023-10-09 2:49 ` [PATCH V8 2/7] acpi: cppc: Add get the highest performance cppc control Meng Li
2023-10-09 2:49 ` [PATCH V8 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting Meng Li
2023-10-09 6:19 ` Wyes Karny
2023-10-10 10:36 ` Peter Zijlstra [this message]
2023-10-11 1:01 ` Meng, Li (Jassmine)
2023-10-09 2:49 ` [PATCH V8 4/7] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-10-09 6:19 ` Wyes Karny
2023-10-09 2:49 ` [PATCH V8 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically Meng Li
2023-10-09 6:19 ` Wyes Karny
2023-10-09 8:08 ` Meng, Li (Jassmine)
2023-10-09 2:49 ` [PATCH V8 6/7] Documentation: amd-pstate: introduce amd-pstate preferred core Meng Li
2023-10-09 6:23 ` Wyes Karny
2023-10-09 2:49 ` [PATCH V8 7/7] Documentation: introduce amd-pstate preferrd core mode kernel command line options Meng Li
2023-10-09 6:54 ` [PATCH V8 0/7] amd-pstate preferred core Oleksandr Natalenko
2023-10-09 7:23 ` Meng, Li (Jassmine)
2023-10-09 12:59 ` Oleksandr Natalenko
2023-10-10 2:15 ` Meng, Li (Jassmine)
2023-10-10 3:01 ` Huang Rui
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=20231010103629.GI377@noisy.programming.kicks-ass.net \
--to=peterz@infradead.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=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