linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Guittot <vincent.guittot@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
	 sudeep.holla@arm.com, viresh.kumar@linaro.org,
	agross@kernel.org,  andersson@kernel.org,
	konrad.dybcio@linaro.org, mingo@redhat.com,
	 peterz@infradead.org, juri.lelli@redhat.com,
	dietmar.eggemann@arm.com,  rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
	 vschneid@redhat.com, lukasz.luba@arm.com, rui.zhang@intel.com,
	 mhiramat@kernel.org, daniel.lezcano@linaro.org,
	amit.kachhap@gmail.com,  corbet@lwn.net,
	gregkh@linuxfoundation.org,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,  linux-pm@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	 linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	 qyousef@layalina.io
Subject: Re: [PATCH v4 1/5] cpufreq: Add a cpufreq pressure feedback for the scheduler
Date: Tue, 9 Jan 2024 18:00:12 +0100	[thread overview]
Message-ID: <CAKfTPtAncXsNa6_8PXfn3Hv0G03WN79QgPQafJqPSo-3oJm6KA@mail.gmail.com> (raw)
In-Reply-To: <CAJZ5v0ixmEiOhwBHkDqH8QNtchiszAEi0rY2pDCGHXiWHob0NA@mail.gmail.com>

On Tue, 9 Jan 2024 at 17:49, Rafael J. Wysocki <rafael@kernel.org> wrote:
>
> On Tue, Jan 9, 2024 at 5:47 PM Vincent Guittot
> <vincent.guittot@linaro.org> wrote:
> >
> > Provide to the scheduler a feedback about the temporary max available
> > capacity. Unlike arch_update_thermal_pressure, this doesn't need to be
> > filtered as the pressure will happen for dozens ms or more.
> >
> > Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
>
> Acked-by: Rafael J. Wysocki <rafael@kernel.org>
>
> and I think I've given the tag on this patch already.

yes, I preferred to not add it after the crap that I did in the v3
with the cleanup of this [1/5] patch

Thanks

>
> > ---
> >  drivers/cpufreq/cpufreq.c | 36 ++++++++++++++++++++++++++++++++++++
> >  include/linux/cpufreq.h   | 10 ++++++++++
> >  2 files changed, 46 insertions(+)
> >
> > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> > index 44db4f59c4cc..f4eee3d107f1 100644
> > --- a/drivers/cpufreq/cpufreq.c
> > +++ b/drivers/cpufreq/cpufreq.c
> > @@ -2563,6 +2563,40 @@ int cpufreq_get_policy(struct cpufreq_policy *policy, unsigned int cpu)
> >  }
> >  EXPORT_SYMBOL(cpufreq_get_policy);
> >
> > +DEFINE_PER_CPU(unsigned long, cpufreq_pressure);
> > +
> > +/**
> > + * cpufreq_update_pressure() - Update cpufreq pressure for CPUs
> > + * @policy: cpufreq policy of the CPUs.
> > + *
> > + * Update the value of cpufreq pressure for all @cpus in the policy.
> > + */
> > +static void cpufreq_update_pressure(struct cpufreq_policy *policy)
> > +{
> > +       unsigned long max_capacity, capped_freq, pressure;
> > +       u32 max_freq;
> > +       int cpu;
> > +
> > +       cpu = cpumask_first(policy->related_cpus);
> > +       max_freq = arch_scale_freq_ref(cpu);
> > +       capped_freq = policy->max;
> > +
> > +       /*
> > +        * Handle properly the boost frequencies, which should simply clean
> > +        * the cpufreq pressure value.
> > +        */
> > +       if (max_freq <= capped_freq) {
> > +               pressure = 0;
> > +       } else {
> > +               max_capacity = arch_scale_cpu_capacity(cpu);
> > +               pressure = max_capacity -
> > +                          mult_frac(max_capacity, capped_freq, max_freq);
> > +       }
> > +
> > +       for_each_cpu(cpu, policy->related_cpus)
> > +               WRITE_ONCE(per_cpu(cpufreq_pressure, cpu), pressure);
> > +}
> > +
> >  /**
> >   * cpufreq_set_policy - Modify cpufreq policy parameters.
> >   * @policy: Policy object to modify.
> > @@ -2618,6 +2652,8 @@ static int cpufreq_set_policy(struct cpufreq_policy *policy,
> >         policy->max = __resolve_freq(policy, policy->max, CPUFREQ_RELATION_H);
> >         trace_cpu_frequency_limits(policy);
> >
> > +       cpufreq_update_pressure(policy);
> > +
> >         policy->cached_target_freq = UINT_MAX;
> >
> >         pr_debug("new min and max freqs are %u - %u kHz\n",
> > diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> > index afda5f24d3dd..b1d97edd3253 100644
> > --- a/include/linux/cpufreq.h
> > +++ b/include/linux/cpufreq.h
> > @@ -241,6 +241,12 @@ struct kobject *get_governor_parent_kobj(struct cpufreq_policy *policy);
> >  void cpufreq_enable_fast_switch(struct cpufreq_policy *policy);
> >  void cpufreq_disable_fast_switch(struct cpufreq_policy *policy);
> >  bool has_target_index(void);
> > +
> > +DECLARE_PER_CPU(unsigned long, cpufreq_pressure);
> > +static inline unsigned long cpufreq_get_pressure(int cpu)
> > +{
> > +       return per_cpu(cpufreq_pressure, cpu);
> > +}
> >  #else
> >  static inline unsigned int cpufreq_get(unsigned int cpu)
> >  {
> > @@ -263,6 +269,10 @@ static inline bool cpufreq_supports_freq_invariance(void)
> >         return false;
> >  }
> >  static inline void disable_cpufreq(void) { }
> > +static inline unsigned long cpufreq_get_pressure(int cpu)
> > +{
> > +       return 0;
> > +}
> >  #endif
> >
> >  #ifdef CONFIG_CPU_FREQ_STAT
> > --
> > 2.34.1
> >

  reply	other threads:[~2024-01-09 17:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 16:46 [PATCH v4 0/5] Rework system pressure interface to the scheduler Vincent Guittot
2024-01-09 16:46 ` [PATCH v4 1/5] cpufreq: Add a cpufreq pressure feedback for " Vincent Guittot
2024-01-09 16:49   ` Rafael J. Wysocki
2024-01-09 17:00     ` Vincent Guittot [this message]
2024-01-10  6:43   ` Viresh Kumar
2024-01-30  0:05   ` Qais Yousef
2024-01-09 16:46 ` [PATCH v4 2/5] sched: Take cpufreq feedback into account Vincent Guittot
2024-01-30  0:26   ` Qais Yousef
2024-01-30  0:50     ` Qais Yousef
2024-01-30  9:35       ` Vincent Guittot
2024-01-30 22:09         ` Qais Yousef
2024-01-09 16:46 ` [PATCH v4 3/5] thermal/cpufreq: Remove arch_update_thermal_pressure() Vincent Guittot
2024-01-09 16:46 ` [PATCH v4 4/5] sched: Rename arch_update_thermal_pressure into arch_update_hw_pressure Vincent Guittot
2024-01-30  0:33   ` Qais Yousef
2024-01-30  0:47   ` Qais Yousef
2024-01-09 16:46 ` [PATCH v4 5/5] sched/pelt: Remove shift of thermal clock Vincent Guittot
2024-01-30  0:36   ` Qais Yousef

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=CAKfTPtAncXsNa6_8PXfn3Hv0G03WN79QgPQafJqPSo-3oJm6KA@mail.gmail.com \
    --to=vincent.guittot@linaro.org \
    --cc=agross@kernel.org \
    --cc=amit.kachhap@gmail.com \
    --cc=andersson@kernel.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=juri.lelli@redhat.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukasz.luba@arm.com \
    --cc=mgorman@suse.de \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rui.zhang@intel.com \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).