Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp296306rwd; Wed, 31 May 2023 23:45:19 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ44T0zGGuJkFJPoUsu0GzzG9pVs/QZWg4DgeZY4CHKlP8fCrSCfngYdAVI15tfrTAe+H4Y6 X-Received: by 2002:a05:6358:7e88:b0:123:5d3c:5a36 with SMTP id o8-20020a0563587e8800b001235d3c5a36mr2831284rwn.24.1685601919471; Wed, 31 May 2023 23:45:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685601919; cv=none; d=google.com; s=arc-20160816; b=FMRz/DTPT+31p/2aMr4Mqtlcz94LnT0sqUD8CnWYQs+wG45PPfpZ9G9QUca0PkOVQg Jp5Iewwc3JayupqfTzhJ7ON6FplTrL37FBjfYmMFwaa3GRPdE48FvSoaIVtJE85UQnV5 xpTB4HdKL9Rx06xw/dKSGbuQ+V80MYxIFSPlo9GI4F5ZEtZi4FvrCv1oD520Q7fTB9PO RVxmN7biiqf2MxfFsq8ooWMzSyhrC4sUFxvqzqJFXWqBUrVxeAex8gbgYpEOaRnK8LZg vxuh7SwPBppOrVOqVamrUu1lqcfuTUrU97DLL94WkFI6tcT2kKsynW3U5vZl1Ka8Fu2G HDxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=9GPIGWt/fVNX5sKFJm1PQZvfe7pXaGIu1cndHbRuzUA=; b=Mae07E5yJQasL8qLxO5g0GJaSc8Lb+yN1n13TO0nZ0sct4/QgPhaY2tiUdAM9Dys04 /u1U/6js0fC/vsnsvqgT5a2w2dcM9I654I43Ad+WkRZdClKGuqAAR6Hca3aKZXGzyaPY 2PpBCnjYCNFxzbbdwR7FjpR7Nh/M6D+/DTRsN1/35YuCNL/vOH2WaJZnrr4LzaoCrBpT sWyS3vhJNUwajKH9PPGOKPBFRuVaWRugtaSAVcPF9dR3Ab2CERvKjwaF1L/OrDrUHGOT j2OWxCmi94ABgY8P2rrzx2NY2YfXrKMe3HR8eYyS5iHIqCRusMEorN7kRksgtzEyFrqw QEZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p3-20020a17090ab90300b0025082583ae6si563547pjr.187.2023.05.31.23.45.07; Wed, 31 May 2023 23:45:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231533AbjFAGcj (ORCPT + 99 others); Thu, 1 Jun 2023 02:32:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47864 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229927AbjFAGci (ORCPT ); Thu, 1 Jun 2023 02:32:38 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B929998; Wed, 31 May 2023 23:32:36 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id DB024169C; Wed, 31 May 2023 23:33:21 -0700 (PDT) Received: from bogus (unknown [10.57.96.86]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D3D063F7D8; Wed, 31 May 2023 23:32:34 -0700 (PDT) Date: Thu, 1 Jun 2023 07:32:31 +0100 From: Sudeep Holla To: Florian Fainelli Cc: Conor Dooley , stable@vger.kernel.org, Pierre Gondois , Conor Dooley , Greg Kroah-Hartman , "Rafael J. Wysocki" , "open list:GENERIC ARCHITECTURE TOPOLOGY" Subject: Re: [PATCH stable 6.3 v2] arch_topology: Remove early cacheinfo error message if -ENOENT Message-ID: <20230601063231.dyvrl37afhk65zit@bogus> References: <20230530201955.848176-1-florian.fainelli@broadcom.com> <20230530-basically-wildly-84415a94171d@spud> <72d84100-55cf-566d-8301-7147ce14b1e9@broadcom.com> <20230531085356.ru4fmtawyxo5cq5s@bogus> <7eae52f6-ca7e-5017-629e-43761d4eb5d7@broadcom.com> <20230531154338.x7rivfpxj2wtjpq6@bogus> <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0f2e3a2b-477b-cbd7-e756-4b3f4df8e045@broadcom.com> X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE 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-kernel@vger.kernel.org On Wed, May 31, 2023 at 12:52:22PM -0700, Florian Fainelli wrote: > > > On 5/31/2023 8:43 AM, Sudeep Holla wrote: > > On Wed, May 31, 2023 at 08:28:26AM -0700, Florian Fainelli wrote: > > > > > > > > > On 5/31/2023 1:53 AM, Sudeep Holla wrote: > > > > On Tue, May 30, 2023 at 03:42:45PM -0700, Florian Fainelli wrote: > > > > > Hi Conor, > > > > > > > > > > On 5/30/23 14:39, Conor Dooley wrote: > > > > > > Yo Florian, > > > > > > > > > > > > On Tue, May 30, 2023 at 01:19:55PM -0700, Florian Fainelli wrote: > > > > > > > From: Pierre Gondois > > > > > > > > > > > > > > commit 3522340199cc060b70f0094e3039bdb43c3f6ee1 upstream > > > > > > > > > > > > > > fetch_cache_info() tries to get the number of cache leaves/levels > > > > > > > for each CPU in order to pre-allocate memory for cacheinfo struct. > > > > > > > Allocating this memory later triggers a: > > > > > > > 'BUG: sleeping function called from invalid context' > > > > > > > in PREEMPT_RT kernels. > > > > > > > > > > > > > > If there is no cache related information available in DT or ACPI, > > > > > > > fetch_cache_info() fails and an error message is printed: > > > > > > > 'Early cacheinfo failed, ret = ...' > > > > > > > > > > > > > > Not having cache information should be a valid configuration. > > > > > > > Remove the error message if fetch_cache_info() fails with -ENOENT. > > > > > > > > > > > > > > Suggested-by: Conor Dooley > > > > > > > Link: https://lore.kernel.org/all/20230404-hatred-swimmer-6fecdf33b57a@spud/ > > > > > > > Signed-off-by: Pierre Gondois > > > > > > > Reviewed-by: Conor Dooley > > > > > > > Link: https://lore.kernel.org/r/20230414081453.244787-4-pierre.gondois@arm.com > > > > > > > Signed-off-by: Sudeep Holla > > > > > > > Signed-off-by: Florian Fainelli > > > > > > > > > > > > How come this now needs a backport? Did the rest of the series get > > > > > > backported, but not this one since it has no fixes tag? > > > > > > > > > > Humm, indeed, this has been present in v6.3.2 since I requested it to be > > > > > included. The error that I saw this morning was not -ENOENT, but -EINVAL. > > > > > > > > > > With those patches applied, no more -EINVAL: > > > > > > > > > > cacheinfo: Allow early level detection when DT/ACPI info is missing/broken > > > > > cacheinfo: Add arm64 early level initializer implementation > > > > > cacheinfo: Add arch specific early level initializer > > > > > cacheinfo: Add use_arch[|_cache]_info field/function > > > > > > > > > > I will submit those shortly unless we think they better not be in 6.3, in > > > > > which case it would be nice to silence those -EINVAL errors. > > > > > > > > I prefer this option instead of back porting all the above 4 as there are > > > > some pending fixes for the issues found in those patches. I am fine if Greg > > > > is happy with the backport, so no strong rejection from my side :). > > > > > > OK, so are you suggesting that we specific check for -EINVAL and -ENOENT > > > rather than take all of the 4 above patches, > > > > Yes that is my preference ATM or if possible to wait until all the fixes > > are sorted for the bugs associated with above 4 commits [1] and [2]. > > I have queued [1] but waiting for response/patch on [2] and hence not yet > > bothered Greg. > > > > > if so, any preference on how to do it given the state of 6.3 stable? > > > > I don't understand what exactly do you mean ? > > Linux 6.3.y currently contains: > > cacheinfo: Check sib_leaf in cache_leaves_are_shared() > cacheinfo: Check cache properties are present in DT > arch_topology: Remove early cacheinfo error message if -ENOENT > > however my logs are full of: > > [ 0.001484] Early cacheinfo failed, ret = -22 > > reverting these 3 patches mentioned above does not eliminate the error. > > What I am asking is if we need a targeted fix for 6.3 like this: > I am fine with that. Please note Greg has now pulled the fixes I pointed. So I am fine if you want to backport the 4 patches discussed earlier as the stable will get the fixes soon which was my main concern earlier. The other issue I pointed should also be resolved soon based on [1] -- Regards, Sudeep [1] https://lore.kernel.org/all/20230531170336.GA22753@ranerica-svr.sc.intel.com