Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1701682
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Eas-dev] [PATCH V5 2/2] cpufreq: Process remote callbacks from any CPU if the platform permits |
| Date | 2017-08-02 05:50 +0200 |
| Message-ID | <u9SPv-4x2-1@gated-at.bofh.it> (permalink) |
| References | <u87fX-dv-9@gated-at.bofh.it> <u87fX-dv-7@gated-at.bofh.it> <u9DdM-3gc-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [Eas-dev] [PATCH V5 2/2] cpufreq: Process remote callbacks from any CPU if the platform permits Pavan Kondeti <pkondeti@codeaurora.org> - 2017-08-01 13:10 +0200 Re: [Eas-dev] [PATCH V5 2/2] cpufreq: Process remote callbacks from any CPU if the platform permits Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-02 05:50 +0200
csiph-web