From: Jie Zhan <zhanjie9@hisilicon.com>
To: Beata Michalska <beata.michalska@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <ionela.voinescu@arm.com>,
<sudeep.holla@arm.com>, <will@kernel.org>,
<catalin.marinas@arm.com>, <vincent.guittot@linaro.org>,
<vanshikonda@os.amperecomputing.com>
Cc: <sumitg@nvidia.com>, <yang@os.amperecomputing.com>,
<lihuisong@huawei.com>, <viresh.kumar@linaro.org>,
<rafael@kernel.org>
Subject: Re: [PATCH v6 3/4] arm64: Provide an AMU-based version of arch_freq_get_on_cpu
Date: Wed, 14 Aug 2024 14:46:16 +0800 [thread overview]
Message-ID: <e2bf18e6-30cc-c85d-5fd4-c2be83922597@hisilicon.com> (raw)
In-Reply-To: <20240603082154.3830591-4-beata.michalska@arm.com>
Hi Beata,
On 03/06/2024 16:21, Beata Michalska wrote:
> With the Frequency Invariance Engine (FIE) being already wired up with
> sched tick and making use of relevant (core counter and constant
> counter) AMU counters, getting the current frequency for a given CPU,
> can be achieved by utilizing the frequency scale factor which reflects
> an average CPU frequency for the last tick period length.
>
> The solution is partially based on APERF/MPERF implementation of
> arch_freq_get_on_cpu.
>
> Suggested-by: Ionela Voinescu <ionela.voinescu@arm.com>
> Signed-off-by: Beata Michalska <beata.michalska@arm.com>
> ---
> arch/arm64/kernel/topology.c | 110 +++++++++++++++++++++++++++++++----
> 1 file changed, 100 insertions(+), 10 deletions(-)
...
> +
> +#define AMU_SAMPLE_EXP_MS 20
> +
> +unsigned int arch_freq_get_on_cpu(int cpu)
> +{
> + struct amu_cntr_sample *amu_sample;
> + unsigned int start_cpu = cpu;
> + unsigned long last_update;
> + unsigned int freq = 0;
> + u64 scale;
> +
> + if (!amu_fie_cpu_supported(cpu) || !arch_scale_freq_ref(cpu))
> + return 0;
> +
> +retry:
> + amu_sample = per_cpu_ptr(&cpu_amu_samples, cpu);
> +
> + last_update = amu_sample->last_update;
> +
> + /*
> + * For those CPUs that are in full dynticks mode,
> + * and those that have not seen tick for a while
> + * try an alternative source for the counters (and thus freq scale),
> + * if available, for given policy:
> + * this boils down to identifying an active cpu within the same freq
> + * domain, if any.
> + */
> + if (!housekeeping_cpu(cpu, HK_TYPE_TICK) ||
> + time_is_before_jiffies(last_update + msecs_to_jiffies(AMU_SAMPLE_EXP_MS))) {
One question here.
The 2nd condition, providing the addtional code in patch 4, would be:
(!idle_cpu(cpu) && time_is_before_jiffies(last_update +
msecs_to_jiffies(AMU_SAMPLE_EXP_MS)))
That means trying another cpu in the same freq domain if this cpu is
running and not having a tick recently.
In this case, if it fails to find an alternative cpu in the following
code, can it just jump to the calculation
part and return an 'old' frequency rather than return 0?
The freq here won't be older than the freq when the cpu went idle last
time -- yet the freq before last idle
is returned if the cpu were idle (patch 4).
> + struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> + int ref_cpu = cpu;
> +
> + if (!policy)
> + goto leave;
> +
> + if (!policy_is_shared(policy)) {
> + cpufreq_cpu_put(policy);
> + goto leave;
> + }
> +
> + do {
> + ref_cpu = cpumask_next_wrap(ref_cpu, policy->cpus,
> + start_cpu, false);
start_cpu is only used here. looks like we can s/start_cpu/cpu/ and
remove its definition above?
> +
> + } while (ref_cpu < nr_cpu_ids && idle_cpu(ref_cpu));
> +
> + cpufreq_cpu_put(policy);
> +
> + if (ref_cpu >= nr_cpu_ids)
> + /* No alternative to pull info from */
> + goto leave;
> +
> + cpu = ref_cpu;
> + goto retry;
> + }
> + /*
> + * Reversed computation to the one used to determine
> + * the arch_freq_scale value
> + * (see amu_scale_freq_tick for details)
> + */
> + scale = arch_scale_freq_capacity(cpu);
> + freq = scale * arch_scale_freq_ref(cpu);
> + freq >>= SCHED_CAPACITY_SHIFT;
> +leave:
> + return freq;
> +}
> +
> static void amu_fie_setup(const struct cpumask *cpus)
> {
> int cpu;
next prev parent reply other threads:[~2024-08-14 6:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 8:21 [PATCH v6 0/4] Add support for AArch64 AMUv1-based arch_freq_get_on_cpu Beata Michalska
2024-06-03 8:21 ` [PATCH v6 1/4] arch_topology: init capacity_freq_ref to 0 Beata Michalska
2024-06-03 8:21 ` [PATCH v6 2/4] arm64: amu: Delay allocating cpumask for AMU FIE support Beata Michalska
2024-06-03 8:21 ` [PATCH v6 3/4] arm64: Provide an AMU-based version of arch_freq_get_on_cpu Beata Michalska
2024-07-10 17:44 ` Vanshidhar Konda
2024-07-17 6:54 ` Beata Michalska
2024-08-14 6:46 ` Jie Zhan [this message]
2024-08-26 7:23 ` Beata Michalska
2024-08-27 13:05 ` Jie Zhan
2024-06-03 8:21 ` [PATCH v6 4/4] arm64: Update AMU-based freq scale factor on entering idle Beata Michalska
2024-07-08 17:10 ` [PATCH v6 0/4] Add support for AArch64 AMUv1-based arch_freq_get_on_cpu Catalin Marinas
2024-07-11 13:59 ` Beata Michalska
2024-08-14 8:05 ` Jie Zhan
2024-08-26 7:24 ` Beata Michalska
2024-08-27 13:03 ` Jie Zhan
[not found] ` <8a9b4e02-a5c6-cb1b-fd32-728fc2c5e741@hisilicon.com>
2024-09-06 9:45 ` Beata Michalska
2024-07-14 0:32 ` Vanshidhar Konda
2024-07-17 6:58 ` Beata Michalska
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=e2bf18e6-30cc-c85d-5fd4-c2be83922597@hisilicon.com \
--to=zhanjie9@hisilicon.com \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=sumitg@nvidia.com \
--cc=vanshikonda@os.amperecomputing.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
/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
all inboxes | Powered by JetHome®