From nobody Sun Jun 21 02:30:31 2026 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CD58E3876DD; Wed, 8 Apr 2026 11:20:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775647217; cv=none; b=NtjAj60nCJ0Ojp0SqiGu0gW44QDxNJpPbETGRKsEATt6/jLp16QPFcKzN33tyFW8W5yCRZuEqCbTfcHkqtIK3undb2GiOs0a0gAEpYtQq3wKXpKGaayOYZb1ZHnhtc+PSG3Zs3ZxM5Q5b9GhNdCD6C2d0UFaGUpYjPHlLJJv9bc= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775647217; c=relaxed/simple; bh=PQBIyjJqdCXhDrI/VRSmmdujSTuPLndbd+05fxqB96s=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=hBLQGy/hhFB0wRC3yV+loEKXd+e0WdrIAAG6O22CDN4tH8hlmSbussmChv9msn4grStioDvrrO/LPWs5BNfecmh14587tfU2SiojiQuHTe1llXSJgR7nTTMn2wh/YpepOQa8km6o0XGcYD0+3/NVr6agABdM2FvghZ7QpmpTnUY= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=OKFhVjkS; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=/60gOVq7; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="OKFhVjkS"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="/60gOVq7" Date: Wed, 08 Apr 2026 11:20:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1775647212; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zhXzw40sOL2aPr4rAGVFn8Wnn7Wk9HLfhV+sZgo64hE=; b=OKFhVjkSU/kdckE7uQziL7HHjHcCDQFHxCZs5rAd6awq3fdsxSevWJ/wixbWokw4s2Nbep Kh9UV2EkspRsC8Yyu9GYnqvF3gg8DSkzTAqs2RXdAlw5isKPttmmHS8vUdTSePAI2LiQDi pd5nvk1x3rfFyzMt2Fb+3SWCnNaa2YAZyvt0RkhAkr0pSPQboGDag67h8DlFqAOj4S+/Da 7uwFFll1INzumQtrWi/7pUEhMtVUDs6/MIUjx2QG68pE8+TMOtrfrxoPyzEH08MrW70dk+ DFVutY84PK2JFQhgGyD2MhQ7+IWNLc91qUM9RondyONf7cdbF4TPDjZB/rDxwQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1775647212; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zhXzw40sOL2aPr4rAGVFn8Wnn7Wk9HLfhV+sZgo64hE=; b=/60gOVq7OetbxxdFEms3YoT7RH093y/zbrcs8SCZEM2PPw5c+YcYHXjPUVMGq1V756s3L8 GQatOlbENucsSTBQ== From: "tip-bot2 for Peter Zijlstra" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: sched/urgent] sched/deadline: Use revised wakeup rule for dl_server Cc: John Stultz , "Peter Zijlstra (Intel)" , Juri Lelli , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20260404102244.GB22575@noisy.programming.kicks-ass.net> References: <20260404102244.GB22575@noisy.programming.kicks-ass.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <177564721088.801717.7436439370807667482.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Precedence: bulk Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The following commit has been merged into the sched/urgent branch of tip: Commit-ID: 14a857056466be9d3d907a94e92a704ac1be149b Gitweb: https://git.kernel.org/tip/14a857056466be9d3d907a94e92a704ac= 1be149b Author: Peter Zijlstra AuthorDate: Sat, 04 Apr 2026 12:22:44 +02:00 Committer: Peter Zijlstra CommitterDate: Wed, 08 Apr 2026 13:11:43 +02:00 sched/deadline: Use revised wakeup rule for dl_server John noted that commit 115135422562 ("sched/deadline: Fix 'stuck' dl_server= ") unfixed the issue from commit a3a70caf7906 ("sched/deadline: Fix dl_server behaviour"). The issue in commit 115135422562 was for wakeups of the server after the deadline; in which case you *have* to start a new period. The case for a3a70caf7906 is wakeups before the deadline. Now, because the server is effectively running a least-laxity policy, it me= ans that any wakeup during the runnable phase means dl_entity_overflow() will be true. This means we need to adjust the runtime to allow it to still run unt= il the existing deadline expires. Use the revised wakeup rule for dl_defer entities. Fixes: 115135422562 ("sched/deadline: Fix 'stuck' dl_server") Reported-by: John Stultz Signed-off-by: Peter Zijlstra (Intel) Acked-by: Juri Lelli Tested-by: John Stultz Link: https://patch.msgid.link/20260404102244.GB22575@noisy.programming.kic= ks-ass.net --- kernel/sched/deadline.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index d08b004..674de6a 100644 --- a/kernel/sched/deadline.c +++ b/kernel/sched/deadline.c @@ -1027,7 +1027,7 @@ static void update_dl_entity(struct sched_dl_entity *= dl_se) if (dl_time_before(dl_se->deadline, rq_clock(rq)) || dl_entity_overflow(dl_se, rq_clock(rq))) { =20 - if (unlikely(!dl_is_implicit(dl_se) && + if (unlikely((!dl_is_implicit(dl_se) || dl_se->dl_defer) && !dl_time_before(dl_se->deadline, rq_clock(rq)) && !is_dl_boosted(dl_se))) { update_dl_revised_wakeup(dl_se, rq);