Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp4239019rwl; Tue, 28 Mar 2023 04:48:25 -0700 (PDT) X-Google-Smtp-Source: AKy350YRGV2B/v/6MMlC3Rx9Sj212tQ/AT5MA8u11n0K/YDha6BKbwe/kZ4iD5mLG3224IuZCJJB X-Received: by 2002:a50:ef01:0:b0:4fb:de7d:b05a with SMTP id m1-20020a50ef01000000b004fbde7db05amr13184875eds.40.1680004104920; Tue, 28 Mar 2023 04:48:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680004104; cv=none; d=google.com; s=arc-20160816; b=0APCpBtNB2KQQUztdyHrbfn81XhyDYqiIGGfE33hXzaiR7DTNC3+RixynhRxJbcTn1 bIxNJYzkes4+RkguvxDnDlih4CSh+LHrewLSDp/0pXXmX2Vh8SHxIoMptzkKcJs2LEEn rTeQU9VbAcvajGVSga4R8GPtT+bwfOid0RVQz0MQgL/zWGqIvVKHNL74eXKFhjv0GTgo +2Q0du2cRsn34QmpufOmImET/UTNsuTasyl1sLjqt6ItPtMbBEgyDXWeDjjg7QbETGHt RrjEDU/AMJx0jcf33XvEjntexs72uPM/swcHNWkH+65CG6L4flqR+Gv4cfJVmLI3TBxy o2uw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:to:subject :cc; bh=k29flBN+rQn8X3+3wqXl8wt2T1J7jut6YQE500toV4s=; b=fLm2R+SLwrdAX2M427BVSfOJwA/fsar7ROmj120upUvQoIM2HNY2l224fyshYwvXQK NigxjMqP3nyHaIN4PJ/yDWQc9EU5e4P+k1D5OfoTlwTANdkGi39Xr3VkGrkd3UDU4fVq Ue3a0BAuE/TuEejVc8WTXlm9VoPhY03AXVlsamnHNmOevRsBEOquZ147yNOqLLsOwkux UWbEnH0v5z3JktDzz2SkFhyfArkjmqqsefxLAh1mVDikUU6QKXckWzIilq76XYTDoS+Y +OLMBs1yATVS91/fYZl7ne4WHgOq5PfOxxOMbUUsFPFUKp66aSWcJZiBRVIjYPkcIDzy /y7Q== 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id o21-20020aa7d3d5000000b004acc6c7a631si28139556edr.179.2023.03.28.04.47.59; Tue, 28 Mar 2023 04:48:24 -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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231174AbjC1Ld3 (ORCPT + 99 others); Tue, 28 Mar 2023 07:33:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53936 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230210AbjC1Ld2 (ORCPT ); Tue, 28 Mar 2023 07:33:28 -0400 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2F72159E0 for ; Tue, 28 Mar 2023 04:33:27 -0700 (PDT) Received: from canpemm500009.china.huawei.com (unknown [172.30.72.55]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4Pm6vB5t0xzKsMr; Tue, 28 Mar 2023 19:31:02 +0800 (CST) Received: from [10.67.102.169] (10.67.102.169) by canpemm500009.china.huawei.com (7.192.105.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Tue, 28 Mar 2023 19:33:24 +0800 CC: , Pierre Gondois , , , , , , Subject: Re: [PATCH] cacheinfo: Fix LLC is not exported through sysfs To: Sudeep Holla References: <20230323122528.16691-1-yangyicong@huawei.com> <7cca5e74-6626-1c8b-9309-47b9f5d4395f@arm.com> <20230324113508.x2rt52aakruwelk3@bogus> <20230328104822.t2p4vxtcwz4j37ec@bogus> From: Yicong Yang Message-ID: <205c2b08-9f75-ddfc-806b-93c1933be2fe@huawei.com> Date: Tue, 28 Mar 2023 19:33:24 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <20230328104822.t2p4vxtcwz4j37ec@bogus> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.102.169] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To canpemm500009.china.huawei.com (7.192.105.203) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-2.3 required=5.0 tests=NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 2023/3/28 18:48, Sudeep Holla wrote: > On Mon, Mar 27, 2023 at 02:57:07PM +0800, Yicong Yang wrote: >> Hi Pierre and Sudeep, >> >> On 2023/3/24 19:35, Sudeep Holla wrote: >>> On Thu, Mar 23, 2023 at 06:58:53PM +0100, Pierre Gondois wrote: >>>> Hello Yicong, >>>> >>>> FWIW, I think the patch is correct and I could reproduce the issue. >>>> >>>> On 3/23/23 13:25, Yicong Yang wrote: >>>>> From: Yicong Yang >>>>> >>>>> After entering 6.3-rc1 the LLC cacheinfo is not exported on our ACPI >>>>> based arm64 server. This is because the LLC cacheinfo is partly reset >>>>> when secondary CPUs boot up. On arm64 the primary cpu will allocate >>>>> and setup cacheinfo: >>>>> init_cpu_topology() >>>>> for_each_possible_cpu() >>>>> fetch_cache_info() // Allocate cacheinfo and init levels >>>>> detect_cache_attributes() >>>>> cache_shared_cpu_map_setup() >>>>> if (!last_level_cache_is_valid()) // not valid, setup LLC >>>>> cache_setup_properties() // setup LLC >>>>> >>>>> On secondary CPU boot up: >>>>> detect_cache_attributes() >>>>> populate_cache_leaves() >>>>> get_cache_type() // Get cache type from clidr_el1, >>>>> // for LLC type=CACHE_TYPE_NOCACHE >>>>> cache_shared_cpu_map_setup() >>>>> if (!last_level_cache_is_valid()) // Valid and won't go to this branch, >>>>> // leave LLC's type=CACHE_TYPE_NOCACHE >>>>> >>>>> The last_level_cache_is_valid() use cacheinfo->{attributes, fw_token} to >>>>> test it's valid or not, but populate_cache_leaves() will only reset >>>>> LLC's type, so we won't try to re-setup LLC's type and leave it >>>>> CACHE_TYPE_NOCACHE and won't export it through sysfs. >>>>> >>> >>> IIUC this is for the case where arch register doesn't report the system level >>> cache. I wonder if it makes sense to fix the arch callback to deal with that >>> instead of here. I am fine either way, just checking as ideally it is >>> something populate_cache_leaves() is messing up. >>> >> >> yes it's right, the LLC information is not provided by the CPU register and can >> only be retrieved from PPTT on my machine. Maybe fix the issue first, I don't >> know how to make arch callback handle this since arch_topology is also used >> other than arm64 which I'm not familiar with. >> >>> [...] >>> >>>>> @@ -481,6 +488,7 @@ int detect_cache_attributes(unsigned int cpu) >>>>> if (ret) >>>>> goto free_ci; >>>>> +update_cpu_map: >>>> >>>> Maybe just a suggestion about the code itself, >>>> it should be possible to replace the 'goto' by an 'if' condition. >>>> (Similarly, the 'populate_leaves:' label could have been avoided.) >>>> >>> >>> Agreed, I prefer that as well. >>> >> >> ok, will modify as below with a little refactor to get rid of the >> 'populate_leaves:' label as suggested. >> >> Thanks, >> Yicong >> >> diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c >> index f6573c335f4c..e34e6b77e81a 100644 >> --- a/drivers/base/cacheinfo.c >> +++ b/drivers/base/cacheinfo.c >> @@ -462,24 +462,28 @@ int detect_cache_attributes(unsigned int cpu) >> * as it will happen only once (the cacheinfo memory is never freed). >> * Just populate the cacheinfo. >> */ >> - if (per_cpu_cacheinfo(cpu)) >> - goto populate_leaves; >> - >> - if (init_cache_level(cpu) || !cache_leaves(cpu)) >> - return -ENOENT; >> + if (!per_cpu_cacheinfo(cpu)) { >> + if (init_cache_level(cpu) || !cache_leaves(cpu)) >> + return -ENOENT; >> >> - ret = allocate_cache_info(cpu); >> - if (ret) >> - return ret; >> + ret = allocate_cache_info(cpu); >> + if (ret) >> + return ret; >> + } >> >> -populate_leaves: >> /* >> - * populate_cache_leaves() may completely setup the cache leaves and >> - * shared_cpu_map or it may leave it partially setup. >> + * If LLC is valid the cache leaves were already populated so just go to >> + * update the cpu map. >> */ >> - ret = populate_cache_leaves(cpu); >> - if (ret) >> - goto free_ci; >> + if (!last_level_cache_is_valid(cpu)) { >> + /* >> + * populate_cache_leaves() may completely setup the cache leaves and >> + * shared_cpu_map or it may leave it partially setup. >> + */ >> + ret = populate_cache_leaves(cpu); >> + if (ret) >> + goto free_ci; >> + } >> >> /* >> * For systems using DT for cache hierarchy, fw_token > > The above looks OK but I would prefer to keep it simple as a fix by just not > adding update_cpu_map label, but I don't have strong opinion about that. So > I am fine either way. > ok got it. I'll respin a v2 patch only involves the fix. Thanks.