mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ananthu C V <ananthu.cv@oss.qualcomm.com>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Danilo Krummrich <dakr@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arch_topology: seed capacity_freq_ref with boost-aware max freq
Date: Mon, 21 Sep 2026 15:57:03 +0530	[thread overview]
Message-ID: <arEGdyvIEXAgltRm@hu-anancv-blr.qualcomm.com> (raw)
In-Reply-To: <CAJZ5v0i_QYa-LcrK1U1VZjZZiJ3d-9hPbMdBbaGoqMds0BAU6w@mail.gmail.com>

Hi Rafael and Vincent,

On Fri, Sep 18, 2026 at 03:32:50PM +0200, Rafael J. Wysocki (Intel) wrote:
> > We keep taking the max between freq table and cpuinfo.max_freq fo the
> > case where the boost freq is not listed is the freq table or there
> > isno freq table. Or there is another way to get teh boost freq in thsi
> > later case ?
> 
> No, I think it's the only way.
> 
> So init_cpu_capacity_callback() should find the highest frequency in
> the table (regardless of whether or not the "boost" flag is set) and
> set capacity_freq_ref to that one for each CPU UUIC.
> 
> That's roughly what the patch does, but it can get away without adding
> a new field to struct cpufreq_policy.
> 
> And the changelog needs to be rewritten to tell the true story.

Thanks for the review. I'll take the suggestions into account and spin up
another revision. The second patch also adds a max_base_freq field, so it
would be nice to know if there are comments on that.

Best,
Ananthu

  parent reply	other threads:[~2026-09-21 10:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  8:30 [PATCH v2 0/2] sched/cpufreq: fix schedutil's boost frequency handling Ananthu C V
2026-09-08  8:30 ` [PATCH v2 1/2] arch_topology: seed capacity_freq_ref with boost-aware max freq Ananthu C V
2026-09-15  7:58   ` Vincent Guittot
2026-09-17 18:10     ` Rafael J. Wysocki (Intel)
2026-09-17 19:05   ` Rafael J. Wysocki (Intel)
2026-09-18  6:23     ` Vincent Guittot
2026-09-18 12:04       ` Rafael J. Wysocki (Intel)
2026-09-18 12:36         ` Vincent Guittot
2026-09-18 13:32           ` Rafael J. Wysocki (Intel)
2026-09-18 13:47             ` Vincent Guittot
2026-09-21 10:27             ` Ananthu C V [this message]
2026-09-08  8:30 ` [PATCH v2 2/2] cpufreq: fix schedutil not returning to non-boost freq when boost is disabled Ananthu C V
2026-09-18  9:15   ` Zhongqiu Han
2026-09-21 10:34     ` Ananthu C V
2026-09-22 13:39       ` Zhongqiu Han
2026-09-08 10:03 ` [PATCH v2 0/2] sched/cpufreq: fix schedutil's boost frequency handling Ananthu C V
2026-09-14 16:27 ` Dietmar Eggemann
2026-09-17 16:05 ` Oleg Keri
2026-09-21 11:57   ` Ananthu C V

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=arEGdyvIEXAgltRm@hu-anancv-blr.qualcomm.com \
    --to=ananthu.cv@oss.qualcomm.com \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --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

all inboxes | Powered by JetHome®