From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: x86 Maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ricardo Neri <ricardo.neri@intel.com>,
Tim Chen <tim.c.chen@intel.com>
Subject: Re: [PATCH v3 2/2] cpufreq: intel_pstate: Set asymmetric CPU capacity on hybrid systems
Date: Fri, 30 Aug 2024 14:00:20 +0530 [thread overview]
Message-ID: <6961a047-979b-40c2-bfc6-d8eddd96694c@linux.ibm.com> (raw)
In-Reply-To: <1979653.PYKUYFuaPT@rjwysocki.net>
On 8/28/24 17:18, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
[...]
>
> +static void hybrid_update_capacity(struct cpudata *cpu)
> +{
> + unsigned int max_cap_perf;
> +
> + mutex_lock(&hybrid_capacity_lock);
> +
> + if (!hybrid_max_perf_cpu)
> + goto unlock;
> +
> + /*
> + * The maximum performance of the CPU may have changed, but assume
> + * that the performance of the other CPUs has not changed.
> + */
> + max_cap_perf = hybrid_max_perf_cpu->capacity_perf;
> +
> + intel_pstate_get_hwp_cap(cpu);
> +
> + hybrid_get_capacity_perf(cpu);
> + /* Should hybrid_max_perf_cpu be replaced by this CPU? */
> + if (cpu->capacity_perf > max_cap_perf) {
> + hybrid_max_perf_cpu = cpu;
> + hybrid_set_capacity_of_cpus();
> + goto unlock;
> + }
> +
> + /* If this CPU is hybrid_max_perf_cpu, should it be replaced? */
> + if (cpu == hybrid_max_perf_cpu && cpu->capacity_perf < max_cap_perf) {
> + hybrid_update_cpu_scaling();
> + goto unlock;
> + }
I assume this CPU capacity is based on freq. It doesnt change based on
irq, any upper scheduler classes such dl, rt right?
can capacity_perf change slightly or it can change such that it always
changes to next possible level? The reason, if it can change slightly,
but cpu is still hybrid_max_perf_cpu, it would end up accessing all the
percpu structures and change it, that would be costly on larger systems.
> +
> + hybrid_set_cpu_capacity(cpu);
> +
> +unlock:
> + mutex_unlock(&hybrid_capacity_lock);
> +}
> +
> static void intel_pstate_hwp_set(unsigned int cpu)
> {
> struct cpudata *cpu_data = all_cpu_data[cpu];
> @@ -1070,6 +1240,22 @@ static void intel_pstate_hwp_offline(str
> value |= HWP_ENERGY_PERF_PREFERENCE(HWP_EPP_POWERSAVE);
>
> wrmsrl_on_cpu(cpu->cpu, MSR_HWP_REQUEST, value);
> +
> + mutex_lock(&hybrid_capacity_lock);
> +
> + if (!hybrid_max_perf_cpu) {
> + mutex_unlock(&hybrid_capacity_lock);
> +
> + return;
> + }
> +
> + if (hybrid_max_perf_cpu == cpu)
> + hybrid_update_cpu_scaling();
> +
> + mutex_unlock(&hybrid_capacity_lock);
> +
> + /* Reset the capacity of the CPU going offline to the initial value. */
> + hybrid_clear_cpu_capacity(cpu->cpu);
>
next prev parent reply other threads:[~2024-08-30 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 11:45 [PATCH v3 0/2] x86 / intel_pstate: Set asymmetric CPU capacity on hybrid systems Rafael J. Wysocki
2024-08-28 11:47 ` [PATCH v3 1/2] x86/sched: Add basic support for CPU capacity scaling Rafael J. Wysocki
2024-09-03 13:57 ` Peter Zijlstra
2024-09-04 6:22 ` Ricardo Neri
2024-09-04 11:24 ` Rafael J. Wysocki
2024-08-28 11:48 ` [PATCH v3 2/2] cpufreq: intel_pstate: Set asymmetric CPU capacity on hybrid systems Rafael J. Wysocki
2024-08-30 8:30 ` Shrikanth Hegde [this message]
2024-08-30 11:10 ` Rafael J. Wysocki
2024-09-03 13:55 ` Peter Zijlstra
2024-09-03 14:02 ` Rafael J. Wysocki
2024-09-04 6:39 ` Ricardo Neri
2024-09-04 11:29 ` Rafael J. Wysocki
2024-09-04 7:25 ` [PATCH v3 0/2] x86 / " Ricardo Neri
2024-09-04 11:30 ` Rafael J. Wysocki
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=6961a047-979b-40c2-bfc6-d8eddd96694c@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=ricardo.neri@intel.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.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