From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Doug Smythies <dsmythies@telus.net>,
Giovanni Gherdovich <ggherdovich@suse.com>
Subject: Re: [RFC][PATCH 1/2] cpufreq: Add special-purpose fast-switching callback for drivers
Date: Thu, 3 Dec 2020 13:41:41 +0100 [thread overview]
Message-ID: <20201203124141.GP3021@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <2174134.tL5yAn4CWt@kreacher>
On Mon, Nov 30, 2020 at 07:37:01PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> First off, some cpufreq drivers (eg. intel_pstate) can pass hints
> beyond the current target frequency to the hardware and there are no
Everything CPPC, which is quite a bit these days.
> + /*
> + * ->fast_switch() replacement for drivers that use an internal
> + * representation of performance levels and can pass hints other than
> + * the target performance level to the hardware.
> + */
> + void (*adjust_perf)(unsigned int cpu, bool busy,
> + unsigned long min_perf,
> + unsigned long target_perf,
> + unsigned long capacity);
>
I'm not sure @busy makes sense, that's more a hack because @util had a
dip and should remain inside schedutil.
> @@ -454,6 +455,25 @@ static void sugov_update_single(struct u
> util = sugov_get_util(sg_cpu);
> max = sg_cpu->max;
> util = sugov_iowait_apply(sg_cpu, time, util, max);
> +
> + /*
> + * This code runs under rq->lock for the target CPU, so it won't run
> + * concurrently on two different CPUs for the same target and it is not
> + * necessary to acquire the lock in the fast switch case.
> + */
> + if (sg_policy->direct_fast_switch) {
> + /*
> + * In this case, any optimizations that can be done are up to
> + * the driver.
> + */
> + cpufreq_driver_adjust_perf(sg_cpu->cpu,
> + sugov_cpu_is_busy(sg_cpu),
> + map_util_perf(sg_cpu->bw_dl),
> + map_util_perf(util), max);
> + sg_policy->last_freq_update_time = time;
> + return;
> + }
Instead of adding more branches, would it makes sense to simply set a
whole different util_hook in this case?
next prev parent reply other threads:[~2020-12-03 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 18:33 [RFC][PATCH 0/2] cpufreq: Allow drivers to receive more information from the governor Rafael J. Wysocki
2020-11-30 18:37 ` [RFC][PATCH 1/2] cpufreq: Add special-purpose fast-switching callback for drivers Rafael J. Wysocki
2020-12-02 15:58 ` Doug Smythies
2020-12-02 17:39 ` Rafael J. Wysocki
2020-12-03 12:41 ` Peter Zijlstra [this message]
2020-12-03 14:44 ` Rafael J. Wysocki
2020-12-07 7:46 ` Viresh Kumar
2020-12-07 13:40 ` Rafael J. Wysocki
2020-11-30 18:37 ` [RFC][PATCH 2/2] cpufreq: intel_pstate: Implement the ->adjust_perf() callback 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=20201203124141.GP3021@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dsmythies@telus.net \
--cc=ggherdovich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).