Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp622364pxb; Tue, 1 Feb 2022 07:10:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJyCjfXO5nCpZa7YnOZvTA/xjyKZvZMM5vw3GB5TKwCpH2bWAOXyNyaqk5As6kZ7cPOT0d7q X-Received: by 2002:a05:6402:40cd:: with SMTP id z13mr25731165edb.119.1643728236384; Tue, 01 Feb 2022 07:10:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643728236; cv=none; d=google.com; s=arc-20160816; b=iYEPZdOvO48mi3MbFiqt6TOJ6+b0UHjJaRoDPrMxS4Z0jH0BlhfFj0sIY/3um4E9Fx VVZFZxfGUbTttcsGGwRyrOdMZiJn3gpBPXdqKr7ydtC3q75Jpp4pK6oOKPutvuVfM7a/ 6qQ74NiqFNRkPvDtlrINczMNUHHWbx2mWUUeikTGwMEAHWrsJm4rrJSLJ04faSfKbJYM iCtohT7yuGWP2H0Pu4R98A0VVpUEAxWWwGJUCliX7Nhx1y9sI8oWg+CWNElJgSZZaZiO mUFofHPdpqsSO4wG+v8LzMIeihtcdDSYbEOxqSjk19kBDypw/u5Dh/aBydT3MKcK0GLS w+Ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:subject:date:cc:to:from; bh=d3+lbHhmSqURO9r6njplByiysKocwVIrU3K4Q09MfAI=; b=DFZ24Yu+QR/ysqgpXEf1oApZehsNF/pLa+vaYNMGAdjD4OlFqvEcEMfHg0engw6m8p Mb5OSaUzAy8ZGDp8G7iurpth2ZHOujgTmaME7BUC4SKCfR1ZvshdeOw/nwDoJ2T4KoMY 8Ot14gY/kIeM223ZJ+HxqVrZ4rY2ro+erwAcKg70Lj7CcfdrIk9B69GcUelq3Li3nfHz t1tCL4zb/LDlYInUiMxKRc0aeb5pQprK7q1CHY71MK6uiO6v53DCRReyDWT7R8YxtnP7 Cwrv+e45tO75Kt+fhskqHXVCipDZtT/QPIh46Y46gGVJ7NYdvA1AO+Gm/Xr0XTQ+L2lQ 3B6w== 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e4si11328684ejs.825.2022.02.01.07.10.10; Tue, 01 Feb 2022 07:10:36 -0800 (PST) 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349997AbiA3WTr (ORCPT + 99 others); Sun, 30 Jan 2022 17:19:47 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45628 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232281AbiA3WTr (ORCPT ); Sun, 30 Jan 2022 17:19:47 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E6325C061714; Sun, 30 Jan 2022 14:19:45 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 55C2C60F56; Sun, 30 Jan 2022 22:19:45 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7992CC340E4; Sun, 30 Jan 2022 22:19:44 +0000 (UTC) X-Mailbox-Line: From 21c067c189901e2f7b368bc1ff6e7216a367c347 Mon Sep 17 00:00:00 2001 From: Clark Williams To: Steven Rostedt , Sebastian Andrzej Siewior Cc: Thomas Gleixner , linux-rt-users@vger.kernel.org, williams@redhat.com, linux-kernel@vger.kernel.org Date: Sun, 30 Jan 2022 15:46:27 -0600 Subject: [PATCH PREEMPT_RT 4.19 STABLE] rt: PREEMPT_RT safety net for backported patches Message-Id: <20220130221944.7992CC340E4@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While doing some 4.19-rt cleanup work, I stumbled across the fact that parts of two backported patches were dependent on CONFIG_PREEMPT_RT, rather than the CONFIG_PREEMPT_RT_FULL used in 4.19 and earlier RT series. The commits in the linux-stable-rt v4.19-rt branch are: dad4c6a33bf4e mm: slub: Don't resize the location tracking cache on PREEMPT_RT e626b6f873f2c net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT Discussing this at the Stable RT maintainers meeting, Steven Rostedt suggested that we automagically select CONFIG_PREEMPT_RT if CONFIG_PREEMPT_RT_FULL is on, giving us a safety net for any subsequently backported patches. Here's my first cut at that patch. I suspect we'll need a similar patch for stable RT kernels < 4.19. Suggested-by: Steven Rostedt Signed-off-by: Clark Williams --- kernel/Kconfig.preempt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/kernel/Kconfig.preempt b/kernel/Kconfig.preempt index 306567f72a3e..951f58cbd652 100644 --- a/kernel/Kconfig.preempt +++ b/kernel/Kconfig.preempt @@ -6,6 +6,10 @@ config PREEMPT_RT_BASE bool select PREEMPT +config PREEMPT_RT + bool + default false + config HAVE_PREEMPT_LAZY bool @@ -80,6 +84,7 @@ config PREEMPT_RT_FULL depends on IRQ_FORCED_THREADING select PREEMPT_RT_BASE select PREEMPT_RCU + select PREEMPT_RT help All and everything -- 2.34.1