From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753211AbdDLO0h (ORCPT ); Wed, 12 Apr 2017 10:26:37 -0400 Received: from mail-pg0-f53.google.com ([74.125.83.53]:33760 "EHLO mail-pg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752209AbdDLO0f (ORCPT ); Wed, 12 Apr 2017 10:26:35 -0400 Date: Wed, 12 Apr 2017 19:56:28 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Ingo Molnar , Peter Zijlstra , Lists linaro-kernel , Linux PM , Linux Kernel Mailing List , Vincent Guittot , Steve Muckle , Juri Lelli , Morten Rasmussen , Patrick Bellasi , eas-dev@lists.linaro.org Subject: Re: [RFC 5/9] sched: cpufreq: remove smp_processor_id() in remote paths Message-ID: <20170412142628.GH5910@vireshk-i7> References: <834d098efe029ee687bac7690bb482e9263a766b.1489058244.git.viresh.kumar@linaro.org> <1836427.bpauTYz19k@aspire.rjw.lan> <20170411103556.GC13627@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11-04-17, 16:00, Rafael J. Wysocki wrote: > On Tue, Apr 11, 2017 at 12:35 PM, Viresh Kumar wrote: > > On 29-03-17, 23:28, Rafael J. Wysocki wrote: > >> On Thursday, March 09, 2017 05:15:15 PM Viresh Kumar wrote: > >> > @@ -216,7 +216,7 @@ static void sugov_update_single(struct update_util_data *hook, u64 time, > >> > if (flags & SCHED_CPUFREQ_RT_DL) { > >> > next_f = policy->cpuinfo.max_freq; > >> > } else { > >> > - sugov_get_util(&util, &max); > >> > + sugov_get_util(&util, &max, hook->cpu); > >> > >> Why is this not racy? > > > > Why would reading the utilization values be racy? The only dynamic value here is > > "util_avg" and I am not sure if reading it is racy. > > > > But, this whole routine has races which I ignored as we may end up updating > > frequency simultaneously from two threads. > > Those races aren't there if we don't update cross-CPU, which is my point. :-) Of course. There are no races without this series. > >> > sugov_iowait_boost(sg_cpu, &util, &max); > >> > next_f = get_next_freq(sg_policy, util, max); > >> > } > >> > @@ -272,7 +272,7 @@ static void sugov_update_shared(struct update_util_data *hook, u64 time, > >> > unsigned long util, max; > >> > unsigned int next_f; > >> > > >> > - sugov_get_util(&util, &max); > >> > + sugov_get_util(&util, &max, hook->cpu); > >> > > >> > >> And here? > >> > >> > raw_spin_lock(&sg_policy->update_lock); > > > > The lock prevents the same here though. > > > > So, if we are going to use this series, then we can use the same update-lock in > > case of single cpu per policies as well. > > No, we can't. > > The lock is unavoidable in the mulit-CPU policies case, but there's no > way I will agree on using a lock in the single-CPU case. How do you suggest to avoid the locking here then ? Some atomic variable read/write as done in cpufreq_governor.c ? -- viresh