From: Christian Loehle <christian.loehle@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Qais Yousef <qyousef@layalina.io>,
Vincent Guittot <vincent.guittot@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Pierre Gondois <pierre.gondois@arm.com>
Subject: Re: [PATCHv2] cpufreq/schedutil: Only bind threads if needed
Date: Mon, 7 Oct 2024 11:42:38 +0100 [thread overview]
Message-ID: <e09f3682-ee0c-4abc-b387-5358bbdf6e79@arm.com> (raw)
In-Reply-To: <CAJZ5v0jpdZBX5tJgdiOvEZbdRJ0kXxT6+uX=s++NG=dNrCMntQ@mail.gmail.com>
On 10/1/24 19:31, Rafael J. Wysocki wrote:
> On Fri, Sep 27, 2024 at 10:59 AM Christian Loehle
> <christian.loehle@arm.com> wrote:
>>
>> Remove the unconditional binding of sugov kthreads to the affected CPUs
>> if the cpufreq driver indicates that updates can happen from any CPU.
>> This allows userspace to set affinities to either save power (waking up
>> bigger CPUs on HMP can be expensive) or increasing performance (by
>> letting the utilized CPUs run without preemption of the sugov kthread).
>>
>> Signed-off-by: Christian Loehle <christian.loehle@arm.com>
>
> Acked-by: Rafael J. Wysocki <rafael@kernel.org>
>
> and I'm assuming that this will go in via tip.
Peter, is that fine with you?
@Juri: I didn't add your (somewhat implied?) ACK on v2, so I'd be happy to
get it on the dl_task_check_affinity() part.
Regards,
Christian
next prev parent reply other threads:[~2024-10-07 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 8:59 [PATCHv2] cpufreq/schedutil: Only bind threads if needed Christian Loehle
2024-10-01 10:01 ` Viresh Kumar
2024-10-01 10:14 ` Vincent Guittot
2024-10-01 18:31 ` Rafael J. Wysocki
2024-10-07 10:42 ` Christian Loehle [this message]
2024-10-24 9:13 ` Christian Loehle
2024-10-31 14:59 ` Christian Loehle
2024-10-07 13:40 ` Juri Lelli
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=e09f3682-ee0c-4abc-b387-5358bbdf6e79@arm.com \
--to=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=rafael@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