From: Viresh Kumar <viresh.kumar@linaro.org>
To: Pavan Kondeti <pkondeti@codeaurora.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Peter Zijlstra <peterz@infradead.org>,
joelaf@google.com, linux-pm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
skannan@codeaurora.org, smuckle.linux@gmail.com,
eas-dev@lists.linaro.org
Subject: Re: [Eas-dev] [PATCH V5 2/2] cpufreq: Process remote callbacks from any CPU if the platform permits
Date: Wed, 2 Aug 2017 09:14:08 +0530 [thread overview]
Message-ID: <20170802034408.GB26689@vireshk-i7> (raw)
In-Reply-To: <CAEU1=Pm5sdV3imHpx7J2dNqYs5Y_mHiNnQt_HccHsgG2P9NyHQ@mail.gmail.com>
On 01-08-17, 16:30, Pavan Kondeti wrote:
> Currently sugov threads in the schedutil governor are pinned to the
> policy CPUs. schedutil can now make use of this new
> dvfs_possible_from_any_cpu flag and avoid the pinning, right?
Actually yes and it would be something as simple as below. Will send a patch for
this if no one reports any problems with this.
diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
index 9deedd5f16a5..6ea12a8c8863 100644
--- a/kernel/sched/cpufreq_schedutil.c
+++ b/kernel/sched/cpufreq_schedutil.c
@@ -471,7 +471,10 @@ static int sugov_kthread_create(struct sugov_policy *sg_policy)
}
sg_policy->thread = thread;
- kthread_bind_mask(thread, policy->related_cpus);
+
+ if (!policy->dvfs_possible_from_any_cpu)
+ kthread_bind_mask(thread, policy->related_cpus);
+
init_irq_work(&sg_policy->irq_work, sugov_irq_work);
mutex_init(&sg_policy->work_lock);
--
viresh
next prev parent reply other threads:[~2017-08-02 3:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 6:46 [PATCH V5 0/2] sched: cpufreq: Allow remote callbacks Viresh Kumar
2017-07-28 6:46 ` [PATCH V5 1/2] sched: cpufreq: Allow remote cpufreq callbacks Viresh Kumar
2017-07-31 21:19 ` Saravana Kannan
2017-07-28 6:46 ` [PATCH V5 2/2] cpufreq: Process remote callbacks from any CPU if the platform permits Viresh Kumar
2017-07-29 3:43 ` Joel Fernandes
2017-07-31 4:00 ` Viresh Kumar
2017-07-31 21:20 ` Saravana Kannan
2017-08-01 11:00 ` [Eas-dev] " Pavan Kondeti
2017-08-02 3:44 ` Viresh Kumar [this message]
2017-08-01 12:01 ` [PATCH V5 0/2] sched: cpufreq: Allow remote callbacks Peter Zijlstra
2017-08-01 23:22 ` 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=20170802034408.GB26689@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=eas-dev@lists.linaro.org \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pkondeti@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=skannan@codeaurora.org \
--cc=smuckle.linux@gmail.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®