Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp127003rwb; Thu, 6 Oct 2022 15:42:17 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4jTD574aXGaV2RMTJRea+BCXCR8O3K+Qa/Os1mZnOx5SGGmM6IyS1lllVrrsKFVpySyF7W X-Received: by 2002:a17:907:847:b0:77f:f489:cc25 with SMTP id ww7-20020a170907084700b0077ff489cc25mr1755130ejb.80.1665096137042; Thu, 06 Oct 2022 15:42:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665096137; cv=none; d=google.com; s=arc-20160816; b=JkSdqtwK2LBMZWl+4xzvLa2iBGowYPkiXqHtnlTLA3WbNmmEpCZu57z8E+GCIc4/oF cde7JAbMEwGFUOe88M63/zooNzeeQzYDEE7OD1iPNPjLdXPNqWDKYCSdJxSDy3iYzixp 5uYKVCGekIpnWiakVCpBCLsw7s6plh0qkfCUz7m5s10NmIAWjsFT6L/ovGeN7xM2rXAB abyn6dM0W/1ao6bXJJgIEzdDyMFt6g6LHkqQfPHf6XrZXoweIdhG4jA6SizzYzJrcejx xyo/KhOugUSKfwtP5S45tTQcghlcaJZ2Wxdi6RlFZph4e3atX4oG4yIC/3dSQx19BAPe d1zg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=Duxug50hyqlUo3vJQebtcrpCMNmKwa8QfgSYdJzoNuM=; b=lf+mpWHUmbK6eaG0n88/2ijoQ69FSdXhn1F+BsGAVEcyknERduo0365gWdXF0K8nbS dZBzdGSgO0SsHi706frVHJ18NyWB+JLESmrJKc742FYI1C+I+N4VvWKZ6punFtuSY0MQ whTdrDjtKtEs9JZynvD13m8r3WO4o+V9ylfwYyLONBSHoOq2QG9FS7duZM9rPucS/8rV m508+Xn9KelMrwUIvvuykdnokoTbtrZIWD2p3S+gkVLtgthg6H9ELX8guDOQE+lET1mp RJ9UL5/N8QzVXks3h3NevFBuePNFwtwDTtalHQjsAFKU+U8sP4xmTQ+0V5+nFOpX0eVS NiEg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@hpe.com header.s=pps0720 header.b=UhZyX7MU; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=hpe.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v4-20020a170906338400b0078d40f7ef1fsi623733eja.330.2022.10.06.15.41.52; Thu, 06 Oct 2022 15:42:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@hpe.com header.s=pps0720 header.b=UhZyX7MU; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=hpe.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231834AbiJFWhW (ORCPT + 99 others); Thu, 6 Oct 2022 18:37:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56206 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229849AbiJFWhV (ORCPT ); Thu, 6 Oct 2022 18:37:21 -0400 Received: from mx0a-002e3701.pphosted.com (mx0a-002e3701.pphosted.com [148.163.147.86]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 044D592593; Thu, 6 Oct 2022 15:37:21 -0700 (PDT) Received: from pps.filterd (m0134422.ppops.net [127.0.0.1]) by mx0b-002e3701.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 296MYusK001006; Thu, 6 Oct 2022 22:37:16 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding; s=pps0720; bh=Duxug50hyqlUo3vJQebtcrpCMNmKwa8QfgSYdJzoNuM=; b=UhZyX7MU0w0HqSuDw3L+7n1VfgicJUNVpqT5yfol8RiGbu2SHXmcDOsDE+GDPG17WbB5 +4a0STX/LZgmBfZLHSGwLsNu9Ly3k4rn26owIePqTqDLTzLeKy280HQ3SqOeeAISp0BU v8+83FTDfuARSYr5Wl+e4Y0B/N+BvfwoLvcgKFMwcksgclqIfIWYK93WzR4SW8okQmb/ djJyx4EOfjQzkWH/zotD2XEMRn0A0wLnO5IHlQvYpZZwn0rhOH5Z+NXYQrzqAVnlHf5N oGNwTh9xPV3BMm42dCGu7cWyAvPUhLMX1s0Exp4tH4oUi3YQIfQrrhspV0V6FtI/6R/X nw== Received: from p1lg14878.it.hpe.com (p1lg14878.it.hpe.com [16.230.97.204]) by mx0b-002e3701.pphosted.com (PPS) with ESMTPS id 3k27xag0ke-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 06 Oct 2022 22:37:15 +0000 Received: from p1lg14885.dc01.its.hpecorp.net (unknown [10.119.18.236]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by p1lg14878.it.hpe.com (Postfix) with ESMTPS id 65B3313949; Thu, 6 Oct 2022 22:32:15 +0000 (UTC) Received: from adevxp033-sys.us.rdlabs.hpecorp.net (unknown [16.231.227.36]) by p1lg14885.dc01.its.hpecorp.net (Postfix) with ESMTP id 162C6803AB6; Thu, 6 Oct 2022 22:32:15 +0000 (UTC) From: Robert Elliott To: herbert@gondor.apana.org.au, davem@davemloft.net, tim.c.chen@linux.intel.com, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Robert Elliott Subject: [RFC PATCH 1/7] rcu: correct CONFIG_EXT_RCU_CPU_STALL_TIMEOUT descriptions Date: Thu, 6 Oct 2022 17:31:45 -0500 Message-Id: <20221006223151.22159-2-elliott@hpe.com> X-Mailer: git-send-email 2.37.3 In-Reply-To: <20221006223151.22159-1-elliott@hpe.com> References: <20221006223151.22159-1-elliott@hpe.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Proofpoint-ORIG-GUID: 3tntthtH4ugWrwTBrPT1WkqFVy2HJArY X-Proofpoint-GUID: 3tntthtH4ugWrwTBrPT1WkqFVy2HJArY X-HPE-SCL: -1 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.895,Hydra:6.0.528,FMLib:17.11.122.1 definitions=2022-10-06_05,2022-10-06_02,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 malwarescore=0 bulkscore=0 adultscore=0 priorityscore=1501 mlxlogscore=999 lowpriorityscore=0 spamscore=0 impostorscore=0 suspectscore=0 phishscore=0 clxscore=1015 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2209130000 definitions=main-2210060133 X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Make the descriptions of CONFIG_EXT_RCU_CPU_STALL_TIMEOUT match the code: - there is no longer a default of 20 ms for Android since commit 1045a06724f3 ("remove CONFIG_ANDROID"), - the code includes a maximum of 21 seconds, evident when specifying 0 which means to use the CONFIG_RCU_STALL_TIMEOUT value (whose default is 60 seconds). Example .config: CONFIG_RCU_CPU_STALL_TIMEOUT=60 CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0 leads to: /sys/module/rcupdate/parameters/rcu_cpu_stall_timeout:60 /sys/module/rcupdate/parameters/rcu_exp_cpu_stall_timeout:21000 Fixes: 1045a06724f3 ("remove CONFIG_ANDROID") Signed-off-by: Robert Elliott --- Documentation/RCU/stallwarn.rst | 9 +++++---- kernel/rcu/Kconfig.debug | 2 +- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/Documentation/RCU/stallwarn.rst b/Documentation/RCU/stallwarn.rst index e38c587067fc..d86a8b47504f 100644 --- a/Documentation/RCU/stallwarn.rst +++ b/Documentation/RCU/stallwarn.rst @@ -168,10 +168,11 @@ CONFIG_RCU_EXP_CPU_STALL_TIMEOUT Same as the CONFIG_RCU_CPU_STALL_TIMEOUT parameter but only for the expedited grace period. This parameter defines the period of time that RCU will wait from the beginning of an expedited - grace period until it issues an RCU CPU stall warning. This time - period is normally 20 milliseconds on Android devices. A zero - value causes the CONFIG_RCU_CPU_STALL_TIMEOUT value to be used, - after conversion to milliseconds. + grace period until it issues an RCU CPU stall warning. + + A zero value causes the CONFIG_RCU_CPU_STALL_TIMEOUT value to be + used, after conversion to milliseconds, limited to a maximum of + 21 seconds. This configuration parameter may be changed at runtime via the /sys/module/rcupdate/parameters/rcu_exp_cpu_stall_timeout, however diff --git a/kernel/rcu/Kconfig.debug b/kernel/rcu/Kconfig.debug index 1b0c41d490f0..4477eeb8a54f 100644 --- a/kernel/rcu/Kconfig.debug +++ b/kernel/rcu/Kconfig.debug @@ -93,7 +93,7 @@ config RCU_EXP_CPU_STALL_TIMEOUT If the RCU grace period persists, additional CPU stall warnings are printed at more widely spaced intervals. A value of zero says to use the RCU_CPU_STALL_TIMEOUT value converted from - seconds to milliseconds. + seconds to milliseconds, limited to a maximum of 21 seconds. config RCU_TRACE bool "Enable tracing for RCU" -- 2.37.3