Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp3369096imm; Thu, 17 May 2018 07:44:28 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqk58Vc2pUXWcJrVH2tXuTR3tp38KllUoEBQEolHzdGWeZBmbB5hEIbwUPdlblwrlJxJDTU X-Received: by 2002:a17:902:868b:: with SMTP id g11-v6mr5349108plo.305.1526568268913; Thu, 17 May 2018 07:44:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526568268; cv=none; d=google.com; s=arc-20160816; b=gSfx21DqYo6M4tdqhasrdtREg+OlPipxRfCKI/hLeu7SgtYay721FhVH6oB4X3dkCO dnZb6xnXv2LiYtaOb3dejI+rRXS3b+YinJ/Y4ZAf1WLFW6e+nTWBJSfUiQ2FgSQ+5Qw0 T8iCP+fGpWS9oZjNDsgTvZjF5M4Awezjczb2UmS7lUtBPtc2d3xmu/yK+nEpSgW1HFQX P36F59sqV8ogw8QuIKvelrWYiU4s0Ts9CJRI6k48kQIcLCbPG1PXXT9r1gyPo/0eHDuu rylWPzE3FL1Dwn3lbvtDtMEjloOXfFbZUrw3eXUp5iKVcJezs50dHaT9hzWN1Nx/Vv5L G9ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=efrATFVT7jExHnWkcFce+6pX6uPo/wYKPdtJqs7vQK8=; b=TcQLkWZiKRiz6j5FlHvt/2+Bz/jY1jdh0VihtL8wWw01662FWjP0pXl5mh5xk24jJ6 mgob0cCzXQ0seOultKP+c2OCudnzJMtkbzl4uYdzS+aj6EMFsAOgTzhXYrDMwvYCJFPu yp85IiRMYH1pJG+XyRq2g85C/+NdPBBLUsSHuaCgaNPvDKCiRNNeY6UT6hsX85mL7G6f A/oXC+6ePKxLa1w/+PHR2RQZKVL/himIo3UVByKgG6jrR185dmTdz4chJJkPDhhq9B4h pCrxbR7Eb48O1EEOGx1CgIbcmpU4kyA9RQTvPLai4SzUxCgIRdgRtERhpSonhlYOqI7t n7CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=jzsJtcst; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d7-v6si3937044pgq.305.2018.05.17.07.44.13; Thu, 17 May 2018 07:44:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=jzsJtcst; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752096AbeEQOoC (ORCPT + 99 others); Thu, 17 May 2018 10:44:02 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:43752 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751481AbeEQOoA (ORCPT ); Thu, 17 May 2018 10:44:00 -0400 Received: by mail-pf0-f194.google.com with SMTP id j20-v6so2204819pff.10 for ; Thu, 17 May 2018 07:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=efrATFVT7jExHnWkcFce+6pX6uPo/wYKPdtJqs7vQK8=; b=jzsJtcst6CHoyjEt7VxHVYiUxqV+x0azCsxKc7n5Ds8soDRSnlauMEoDWLmZ8IGi6j DCHxHDo4EFj4gYz25T7ln7UVD5WSbxmQ1IazSMn6TMze1aIqc1B2r/xob0vUJsJM8SWL 9QbAobFjgW85uTCW4P2cFyFGFX5y3C/rYPH/8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=efrATFVT7jExHnWkcFce+6pX6uPo/wYKPdtJqs7vQK8=; b=RJRxzIaawlRbdXPsv2+T47GwWqN0qUzEZmI5PS66uaslk5iAxxu+ngxGc+wrSFZsYL VVV2cpba+ISc/l0lxt5tq8TIcBqeWWfW3DejYr3rBmVt/iAfyHlHPj244J5olSd3YP9L 9Q0/JvBzOA/jI+5KSRg2fI3XnbGzhEz1NXSLo4x8fw29K0yhFYdxXgXYAt4Ny+UuvuMF 6c3Nq9adVyuXAXc1h3GWZdt1/eKvMUhKcETBV1iF2i+WMUpfDtT4Hu2vOa3nQAQMx6VR FtcorfU4nZQf95A12aYblcz5ZXcL1Atg50AHsCPUsh2rkCJReQRD8VJ0/7FsX9nOPNjn 6vgg== X-Gm-Message-State: ALKqPwdQbTjgLx6GBOZD1g32EwMa5VJVOrW2dIGJGXsWc6QRKH9youdw 50P8OxyiLXcFVBuTjM6N08kP/g== X-Received: by 2002:a62:e04c:: with SMTP id f73-v6mr5489732pfh.88.1526568240150; Thu, 17 May 2018 07:44:00 -0700 (PDT) Received: from localhost ([2620:0:1000:1600:3122:ea9c:d178:eb]) by smtp.gmail.com with ESMTPSA id p24-v6sm10787641pfk.58.2018.05.17.07.43.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 17 May 2018 07:43:59 -0700 (PDT) Date: Thu, 17 May 2018 07:43:59 -0700 From: Joel Fernandes To: Juri Lelli Cc: Viresh Kumar , linux-kernel@vger.kernel.org, "Rafael J . Wysocki" , Peter Zijlstra , Ingo Molnar , Patrick Bellasi , Luca Abeni , linux-pm@vger.kernel.org, kernel-team@android.com Subject: Re: [PATCH RFC] schedutil: Allow cpufreq requests to be made even when kthread kicked Message-ID: <20180517144359.GA162290@joelaf.mtv.corp.google.com> References: <20180516224518.109891-1-joel@joelfernandes.org> <20180517070026.GA22493@localhost.localdomain> <20180517102024.s3dxo4uepujh5f65@vireshk-i7> <20180517105358.GB22493@localhost.localdomain> <20180517130704.GA139147@joelaf.mtv.corp.google.com> <20180517142823.GD22493@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180517142823.GD22493@localhost.localdomain> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 17, 2018 at 04:28:23PM +0200, Juri Lelli wrote: [...] > > > > We would need more locking stuff in the work handler in that case and > > > > I think there maybe a chance of missing the request in that solution > > > > if the request happens right at the end of when sugov_work returns. > > > > > > Mmm, true. Ideally we might want to use some sort of queue where to > > > atomically insert requests and then consume until queue is empty from > > > sugov kthread. > > > > IMO we don't really need a queue or anything, we should need the kthread to > > process the *latest* request it sees since that's the only one that matters. > > Yep, makes sense. > > > > But, I guess that's going to be too much complexity for an (hopefully) > > > corner case. > > > > I thought of this corner case too, I'd argue its still an improvement over > > not doing anything, but we could tighten this up a bit more if you wanted by > > Indeed! :) > > > doing something like this on top of my patch. Thoughts? > > > > ---8<----------------------- > > > > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c > > index a87fc281893d..e45ec24b810b 100644 > > --- a/kernel/sched/cpufreq_schedutil.c > > +++ b/kernel/sched/cpufreq_schedutil.c > > @@ -394,6 +394,7 @@ static void sugov_work(struct kthread_work *work) > > unsigned int freq; > > unsigned long flags; > > > > +redo_work: > > /* > > * Hold sg_policy->update_lock shortly to handle the case where: > > * incase sg_policy->next_freq is read here, and then updated by > > @@ -409,6 +410,9 @@ static void sugov_work(struct kthread_work *work) > > __cpufreq_driver_target(sg_policy->policy, freq, > > CPUFREQ_RELATION_L); > > mutex_unlock(&sg_policy->work_lock); > > + > > + if (sg_policy->work_in_progress) > > + goto redo_work; > > Didn't we already queue up another irq_work at this point? Oh yeah, so the case I was thinking was if the kthread was active, while the new irq_work raced and finished. Since that would just mean a new kthread_work for the worker, the loop I mentioned above isn't needed. Infact there's already a higher level loop taking care of it in kthread_worker_fn as below. So the governor thread will not sleep and we'll keep servicing all pending requests till they're done. So I think we're good with my original patch. repeat: [...] if (!list_empty(&worker->work_list)) { work = list_first_entry(&worker->work_list, struct kthread_work, node); list_del_init(&work->node); } worker->current_work = work; spin_unlock_irq(&worker->lock); if (work) { __set_current_state(TASK_RUNNING); work->func(work); } else if (!freezing(current)) schedule(); try_to_freeze(); cond_resched(); goto repeat;