Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp1410125pxj; Fri, 18 Jun 2021 06:34:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwp6h2oY2yVArKRNsK6JtlwiNjzV0omGO5/LPzXF1zkbQw+ndNWE2Q2vnPwbPyb/SehMtM1 X-Received: by 2002:a02:a710:: with SMTP id k16mr3402685jam.46.1624023249180; Fri, 18 Jun 2021 06:34:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624023249; cv=none; d=google.com; s=arc-20160816; b=SZCsMKKPNzWALB8fhnrWaT+x7BR3AIFwRF4sOAOZdUECTbZuJ7bduoCNw6Xq3NteUt kgYwRo6TZ0nOYhcZK9sxpg9u6Tt/8DXT17NNtEHGDtRoEjSj8ochZwMslGkoAgZBwBjg VwNagxPgi+wre45+3QSWCJM9JHrl2aaPeMms2ESARxKuLydmA2oUUlT0ifFV0aCRcAQ2 vzFHYrXuNC6qzAXcvgtboCqo0sLyx4Q5jqacxtStec8n5ElPbcRy59dX9BMIMLmzPjGV JVhwnbhu10Xda2CDqinv3Hr7IjkdbnA/BUQFJuSq/ZKsrNTaQhJ7yCSN3bnpBdzmFV29 pkbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from; bh=5lCRKdyPGthiuEU2byCdjJzjojd8OhsNyPXwPeJpCQA=; b=oyTDYU6EBdCoNJW/PAdZf0lol6Zi9WsBNE99eTPtpQUkshyPJfEJpR4h2z2TKLTDJP VmDwQbrKlxBfwwh37qHFUPbc8ZZwzacJMMsy1ZQFu/pRFHlrmOifswZuNo1x/5Fkx8Dp e1P7aNkQC/puuq048y42T9mxtMB8S9nQE0F7ki5N6eAH0cJwx1vPKfuv1OeDsMZXnGzx ICbAzq1tHEke+oIgssJVyw7IIiMGbrrXIoWETmvk+If48QBQAvt1f1h5e7qRnZp+PcFp NSE9uI+vYs1N/WlBdKC86jR3fZsowESiMAZHCFZQ3yk6pMCjsq9Rp9sWGj0uIUSfVMLm dL4g== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r14si9023693jad.0.2021.06.18.06.33.56; Fri, 18 Jun 2021 06:34:09 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233756AbhFRNev (ORCPT + 99 others); Fri, 18 Jun 2021 09:34:51 -0400 Received: from foss.arm.com ([217.140.110.172]:41192 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232258AbhFRNet (ORCPT ); Fri, 18 Jun 2021 09:34:49 -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 538271476; Fri, 18 Jun 2021 06:32:40 -0700 (PDT) Received: from e120877-lin.cambridge.arm.com (e120877-lin.cambridge.arm.com [10.1.194.43]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 1CAD23F719; Fri, 18 Jun 2021 06:32:39 -0700 (PDT) From: Vincent Donnefort To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com Cc: vincent.guittot@linaro.org, dietmar.eggemann@arm.com, valentin.schneider@arm.com, rostedt@goodmis.org, linux-kernel@vger.kernel.org, Vincent Donnefort Subject: [PATCH 2/2] sched/rt: Fix Deadline utilization tracking during policy change Date: Fri, 18 Jun 2021 14:32:19 +0100 Message-Id: <1624023139-66147-2-git-send-email-vincent.donnefort@arm.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1624023139-66147-1-git-send-email-vincent.donnefort@arm.com> References: <1624023139-66147-1-git-send-email-vincent.donnefort@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org DL keeps track of the utilization on a per-rq basis with the structure avg_dl. This utilization is updated during task_tick_dl(), put_prev_task_dl() and set_next_task_dl(). However, when the current running task changes its policy, set_next_task_dl() which would usually take care of updating the utilization when the rq starts running DL tasks, will not see a such change, leaving the avg_dl structure outdated. When that very same task will be dequeued later, put_prev_task_dl() will then update the utilization, based on a wrong last_update_time, leading a huge spike in the DL utilization signal. The signal would eventually recover from this issue after few ms. Even if no DL tasks are run, avg_dl is also updated in __update_blocked_others(). But as the CPU capacity depends partly on the avg_dl, this issue has nonetheless a significant impact on the scheduler. Fix this issue by ensuring a load update when a running task changes its policy to DL. Fixes: 3727e0e ("sched/dl: Add dl_rq utilization tracking") Signed-off-by: Vincent Donnefort diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index 3829c5a..915227a 100644 --- a/kernel/sched/deadline.c +++ b/kernel/sched/deadline.c @@ -2497,6 +2497,8 @@ static void switched_to_dl(struct rq *rq, struct task_struct *p) check_preempt_curr_dl(rq, p, 0); else resched_curr(rq); + } else { + update_dl_rq_load_avg(rq_clock_pelt(rq), rq, 0); } } -- 2.7.4