Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp356667ybt; Fri, 19 Jun 2020 03:40:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz13NGsLlKLzbwBwSS55FE3Uzwjt3DLE0FGkJrVP9N6634fhQ1zakmdw43fTRfTIFuAvogg X-Received: by 2002:a17:906:e2d5:: with SMTP id gr21mr2859251ejb.219.1592563257202; Fri, 19 Jun 2020 03:40:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592563257; cv=none; d=google.com; s=arc-20160816; b=ucG2Y4mNB5WT8sq40mYnp8Nm06A8MsYCWXoL6UJuC/o9h3b6KZTKfkCVeXQB70Tm7/ YXlBeZx6W9gM6ECUABowPAynakIED0wdFZwhHhXP0LASowpaTMNOqjQmqlmsiwhVOvZz LPl7CqIcVdXcZHflhl2NCRUIS8rybW0OPYhEgxH6og0S5TK6PMN4xY2hpw6TN2cg9RVG UwydE8rsQjAsVIqRjGR2zgzhFRpPCn6dMY7aC99+ByqXO1sKnaIadbXqrlEuRNcrjHUd yHfc7rNL79+snCLeTE4RsNgMDay6OIvEzcP7N8g6e0WeZlIGg7W8+t9rpuATSb3aPRl5 kFBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:in-reply-to :subject:cc:to:from:user-agent:references; bh=9W8scfHSQAWrxtKJViSaA3PmGn/5A8CY0c8A/pWcVR0=; b=G3pOZ8K9Sn/GFMeiHe/DU099ZUiDoHmm34p12WS82sFiHPOUhhbNIkoy1t93SibNvr gBHhi0lT1vE5XpL7eniTgYCIVsSjVr1LPWR/m/Y91H68v/gdg9oFHcgrczs6kVKrvRnT s3v1mx7f90sGhtJyUTx0EH/8E72T7rPyJBi2pBHY1ZF22Dn9m9a5rATb2FUt8Be1Ui0a F6mpB0qg1KP/Lka3KwNU7L4MCO0FRFIINGB8Q662qKoFu3cpNstJy0zSbpJ97o+ArHMD A0vP2SlzbHcolSfGXtA3mP57AgkSegBLaKqprnuTF3VT2Azp0Bo9NEXf97xvc5PusBYI QYfA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s3si3427228ejq.532.2020.06.19.03.40.34; Fri, 19 Jun 2020 03:40:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732362AbgFSKg1 (ORCPT + 99 others); Fri, 19 Jun 2020 06:36:27 -0400 Received: from foss.arm.com ([217.140.110.172]:51180 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729195AbgFSKgZ (ORCPT ); Fri, 19 Jun 2020 06:36:25 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 50909D6E; Fri, 19 Jun 2020 03:36:24 -0700 (PDT) Received: from e113632-lin (e113632-lin.cambridge.arm.com [10.1.194.46]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A0EB03F71F; Fri, 19 Jun 2020 03:36:22 -0700 (PDT) References: <20200618195525.7889-1-qais.yousef@arm.com> <20200618195525.7889-2-qais.yousef@arm.com> User-agent: mu4e 0.9.17; emacs 26.3 From: Valentin Schneider To: Qais Yousef Cc: Ingo Molnar , Peter Zijlstra , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Patrick Bellasi , Chris Redpath , Lukasz Luba , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] sched/uclamp: Fix initialization of strut uclamp_rq In-reply-to: <20200618195525.7889-2-qais.yousef@arm.com> Date: Fri, 19 Jun 2020 11:36:17 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 18/06/20 20:55, Qais Yousef wrote: > struct uclamp_rq was zeroed out entirely in assumption that in the first > call to uclamp_rq_inc() they'd be initialized correctly in accordance to > default settings. > > But when next patch introduces a static key to skip > uclamp_rq_{inc,dec}() until userspace opts in to use uclamp, schedutil > will fail to perform any frequency changes because the > rq->uclamp[UCLAMP_MAX].value is zeroed at init and stays as such. Which > means all rqs are capped to 0 by default. > > Fix it by making sure we do proper initialization at init without > relying on uclamp_rq_inc() doing it later. > > Fixes: 69842cba9ace ("sched/uclamp: Add CPU's clamp buckets refcounting") > Signed-off-by: Qais Yousef > Cc: Juri Lelli > Cc: Vincent Guittot > Cc: Dietmar Eggemann > Cc: Steven Rostedt > Cc: Ben Segall > Cc: Mel Gorman > CC: Patrick Bellasi > Cc: Chris Redpath > Cc: Lukasz Luba > Cc: linux-kernel@vger.kernel.org Small nit below, otherwise: Reviewed-by: Valentin Schneider > --- > kernel/sched/core.c | 17 +++++++++++++++-- > 1 file changed, 15 insertions(+), 2 deletions(-) > > diff --git a/kernel/sched/core.c b/kernel/sched/core.c > index a43c84c27c6f..e19d2b915406 100644 > --- a/kernel/sched/core.c > +++ b/kernel/sched/core.c > @@ -1248,6 +1248,20 @@ static void uclamp_fork(struct task_struct *p) > } > } > > +static void __init init_uclamp_rq(struct rq *rq) > +{ > + enum uclamp_id clamp_id; > + struct uclamp_rq *uc_rq = rq->uclamp; > + > + for_each_clamp_id(clamp_id) { > + memset(uc_rq[clamp_id].bucket, > + 0, > + sizeof(struct uclamp_bucket)*UCLAMP_BUCKETS); > + > + uc_rq[clamp_id].value = uclamp_none(clamp_id); > + } > +} > + > static void __init init_uclamp(void) > { > struct uclamp_se uc_max = {}; > @@ -1257,8 +1271,7 @@ static void __init init_uclamp(void) > mutex_init(&uclamp_mutex); > > for_each_possible_cpu(cpu) { > - memset(&cpu_rq(cpu)->uclamp, 0, > - sizeof(struct uclamp_rq)*UCLAMP_CNT); > + init_uclamp_rq(cpu_rq(cpu)); > cpu_rq(cpu)->uclamp_flags = 0; That flags assignment ought to be squashed in the init function as well - and actually you do that in patch 2, so I suppose that's a rebase accident. > }