From nobody Tue Dec 2 02:51:55 2025 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 B8C322D7387; Mon, 17 Nov 2025 16:23:40 +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=1763396622; cv=none; b=P+S3ZqK3494cBse5bbUPYSBiFdHGsj/N1ybmCvN+a0L4JRzf813IIYPqLSrGfPTuyrfQy1dE0r16ATjK9ILmyBOrhC01rUxnUdFl9zZdGrZOAEnWalo0SKWVotavVUMYIqrweDOC2PJ8tuP3G80GOoFzcWGzAm88dMTgBNAM43A= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763396622; c=relaxed/simple; bh=aPg18SEb0LFEmXB7DVgxzAtR/qlLuUPXCLIJLrj2zcY=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=NSJUFjL0S3Yfga/eilM1kA8reaWD8fxs6FGXcwNijPTuJvVnKjjAzyteOgCresseByyYbRbvQyqFb9w2SbBmWM9xDqLJq1eaV7hsdR3hGR+LBRc6P96SfT49x8++1r4tFGyXkmw6D2O3QX09AjFxVN+DLC1ycZsvLQRyHCvjdJY= 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=yT+Euxwn; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=+sVptxSD; 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="yT+Euxwn"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="+sVptxSD" Date: Mon, 17 Nov 2025 16:23:38 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1763396619; 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=PogVt5F9DRDlIZ+UYGkQGMUsbkeTeJuypswSe4UKuvE=; b=yT+EuxwnVSQFnJkhj5HsUL1HdlsHOGcj8XU0aiMsIdfB4sASv8eGAABe7o0/INUfPvz/zn Gf6alev9kUcWJl0uBW0CGo9CzmdxC5scH4GQfAAVeO3re+iZJhiEYn1/4lWcrBmf8od4pJ 5i7Dft18+RJ6AsD6FuYfY4NSk4luXdTcs07s6mFCOeSzK+d+TLFLKDkTGuKZC8ia91RcFT r06TTjaosemOqOqbA5BdJmxwD2vdmXdZSgWU+Cc8ylZlCS0Pg2S5Rt9CAlQLA5MWD53k3t dUAD06nFVDRRy6e/kizRNLe97GSYFLGlchtTeL3mNgMhDEHL+c5IJDXbM3obig== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1763396619; 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=PogVt5F9DRDlIZ+UYGkQGMUsbkeTeJuypswSe4UKuvE=; b=+sVptxSDB1Y4zHBjlZxBV9cO9LAoDaDzDI+pJfpfslzXb4I8mhfiUS18Mq84CyWDQD8n6W R3nNDJVPGVphAcAw== 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/core] sched/fair: Have SD_SERIALIZE affect newidle balancing Cc: Shrikanth Hegde , "Peter Zijlstra (Intel)" , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: =?utf-8?q?=3C6fed119b723c71552943bfe5798c93851b30a361=2E1762800?= =?utf-8?q?251=2Egit=2Etim=2Ec=2Echen=40linux=2Eintel=2Ecom=3E?= References: =?utf-8?q?=3C6fed119b723c71552943bfe5798c93851b30a361=2E17628002?= =?utf-8?q?51=2Egit=2Etim=2Ec=2Echen=40linux=2Eintel=2Ecom=3E?= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <176339661833.498.2066034480120890702.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/core branch of tip: Commit-ID: 522fb20fbdbe48ed98f587d628637ff38ececd2d Gitweb: https://git.kernel.org/tip/522fb20fbdbe48ed98f587d628637ff38= ececd2d Author: Peter Zijlstra AuthorDate: Mon, 17 Nov 2025 17:13:09 +01:00 Committer: Peter Zijlstra CommitterDate: Mon, 17 Nov 2025 17:13:09 +01:00 sched/fair: Have SD_SERIALIZE affect newidle balancing Also serialize the possiblty much more frequent newidle balancing for the 'expensive' domains that have SD_BALANCE set. Initial benchmarking by K Prateek and Tim showed no negative effect. Split out from the larger patch moving sched_balance_running around for ease of bisect and such. Suggested-by: Shrikanth Hegde Seconded-by: K Prateek Nayak Signed-off-by: Peter Zijlstra (Intel) Link: https://lkml.kernel.org/r/df068896-82f9-458d-8fff-5a2f654e8ffd@amd.com Link: https://patch.msgid.link/6fed119b723c71552943bfe5798c93851b30a361.176= 2800251.git.tim.c.chen@linux.intel.com # Conflicts: # kernel/sched/fair.c --- kernel/sched/fair.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 59b17f0..071e07f 100644 --- a/kernel/sched/fair.c +++ b/kernel/sched/fair.c @@ -11732,7 +11732,7 @@ redo: goto out_balanced; } =20 - if (!need_unlock && (sd->flags & SD_SERIALIZE) && idle !=3D CPU_NEWLY_IDL= E) { + if (!need_unlock && (sd->flags & SD_SERIALIZE)) { int zero =3D 0; if (!atomic_try_cmpxchg_acquire(&sched_balance_running, &zero, 1)) goto out_balanced;