public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>, Wyes Karny <wyes.karny@amd.com>
Subject: Re: [PATCH V5 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically
Date: Fri, 8 Sep 2023 15:27:54 +0200	[thread overview]
Message-ID: <20230908132754.GI19320@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20230905015116.2268926-6-li.meng@amd.com>

On Tue, Sep 05, 2023 at 09:51:14AM +0800, Meng Li wrote:

> +static void amd_pstate_update_highest_perf(unsigned int cpu)
> +{
> +	struct cpufreq_policy *policy;
> +	struct amd_cpudata *cpudata;
> +	u32 prev_high = 0, cur_high = 0;
> +	u64 highest_perf;
> +	int ret;
> +
> +	if (!prefcore)
> +		return;
> +
> +	ret = amd_pstate_get_highest_perf(cpu, &highest_perf);
> +	if (ret)
> +		return;
> +
> +	policy = cpufreq_cpu_get(cpu);
> +	cpudata = policy->driver_data;
> +	cur_high = highest_perf;
> +	prev_high = READ_ONCE(cpudata->cppc_highest_perf);
> +
> +	if (prev_high != cur_high) {
> +		WRITE_ONCE(cpudata->cppc_highest_perf, cur_high);
> +		sched_set_itmt_core_prio(cur_high, cpu);

I just noticed, your cur_high is explicitly 'u32', but
sched_set_itmt_core_prio() and the rest of the scheduler use 'int' (aka
s32). If you somehow get that top bit set things might not work out as
expected.

Please double check.

> +	}
> +
> +	cpufreq_cpu_put(policy);
> +}

  parent reply	other threads:[~2023-09-08 13:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  1:51 [PATCH V5 0/7] amd-pstate preferred core Meng Li
2023-09-05  1:51 ` [PATCH V5 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion Meng Li
2023-09-05 22:32   ` Mario Limonciello
2023-09-06 13:09   ` Huang Rui
2023-09-05  1:51 ` [PATCH V5 2/7] acpi: cppc: Add get the highest performance cppc control Meng Li
2023-09-06 13:11   ` Huang Rui
2023-09-05  1:51 ` [PATCH V5 3/7] cpufreq: amd-pstate: Enable amd-pstate preferred core supporting Meng Li
2023-09-05 22:33   ` Mario Limonciello
2023-09-06  3:02   ` kernel test robot
2023-09-06 12:11   ` kernel test robot
2023-09-06 13:52   ` Huang Rui
2023-09-08  6:54     ` Meng, Li (Jassmine)
2023-09-06 18:34   ` Wyes Karny
2023-09-08 13:12   ` Peter Zijlstra
2023-09-08 13:17   ` Peter Zijlstra
2023-09-05  1:51 ` [PATCH V5 4/7] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-09-08 13:19   ` Peter Zijlstra
2023-09-08 13:24   ` Peter Zijlstra
2023-09-11  8:43     ` Meng, Li (Jassmine)
2023-09-05  1:51 ` [PATCH V5 5/7] cpufreq: amd-pstate: Update amd-pstate preferred core ranking dynamically Meng Li
2023-09-06 13:57   ` Huang Rui
2023-09-06 17:49   ` Wyes Karny
2023-09-08 13:27   ` Peter Zijlstra [this message]
2023-09-08 13:28   ` Peter Zijlstra
2023-09-05  1:51 ` [PATCH V5 6/7] Documentation: amd-pstate: introduce amd-pstate preferred core Meng Li
2023-09-06 22:01   ` kernel test robot
2023-09-05  1:51 ` [PATCH V5 7/7] Documentation: introduce amd-pstate preferrd core mode kernel command line options Meng Li

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=20230908132754.GI19320@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=wyes.karny@amd.com \
    --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