From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8AD2BC433ED for ; Thu, 13 May 2021 14:22:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6A1D36143C for ; Thu, 13 May 2021 14:22:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234391AbhEMOXj (ORCPT ); Thu, 13 May 2021 10:23:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:52796 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234416AbhEMOX0 (ORCPT ); Thu, 13 May 2021 10:23:26 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id BEA8D613BC; Thu, 13 May 2021 14:22:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1620915736; bh=G4vCXEGiMxTe526VUaPffNnPoAYhrWSx6k1fW7Br7iA=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=JeScwqKGVsgr8dhA6KWFOjRAaoDSlcmtHzUWvf6gUXHzloUyQoJxbsaB4huYd3P36 lAFHgMB2WIX4en8vqNUCsk05TNuzhIyf8ed4r1qYS91kZ14pbCNfs8LvFaoXtazihE qVFpkOidoo2M0iOyZG3iersgwhHkFrUl8DNJkAtDEqxF/Qie9y8TjIW1k46BydMDKY OuhWmqohwaD6MA1RXvT2/c/BjCkRCKM3YETSZnE+rLWXLppMJPgaJEZUUxKow5XWKX lowu3OXrZ/6mMjI3OWpXc8bCAuD9mrDDMC+QqzkJJ2hV6jRfsTVx1id1buvsoigxZT unJPgCEppFlDQ== Received: by paulmck-ThinkPad-P17-Gen-1.home (Postfix, from userid 1000) id 8100C5C014E; Thu, 13 May 2021 07:22:16 -0700 (PDT) Date: Thu, 13 May 2021 07:22:16 -0700 From: "Paul E. McKenney" To: Ingo Molnar Cc: Paul Gortmaker , linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Frederic Weisbecker Subject: Re: [PATCH] sched/isolation: reconcile rcu_nocbs= and nohz_full= Message-ID: <20210513142216.GZ975577@paulmck-ThinkPad-P17-Gen-1> Reply-To: paulmck@kernel.org References: <20210419042659.1134916-1-paul.gortmaker@windriver.com> <20210422212448.GJ975577@paulmck-ThinkPad-P17-Gen-1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 13, 2021 at 02:13:28PM +0200, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > On Mon, Apr 19, 2021 at 12:26:59AM -0400, Paul Gortmaker wrote: > > > We have a mismatch between RCU and isolation -- in relation to what is > > > considered the maximum valid CPU number. > > > > > > This matters because nohz_full= and rcu_nocbs= are joined at the hip; in > > > fact the former will enforce the latter. So we don't want a CPU mask to > > > be valid for one and denied for the other. > > > > > > The difference 1st appeared as of v4.15; further details are below. > > > > I pulled this into -rcu for testing and further review. > > > > If it should instead go through some other tree: > > > > Acked-by: Paul E. McKenney > > Thanks - added this fix to tip:sched/core. Very good, I will drop it from -rcu later today, Pacific Time. Thanx, Paul