Received: by 2002:a05:7412:518d:b0:e2:908c:2ebd with SMTP id fn13csp341936rdb; Thu, 5 Oct 2023 07:33:13 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFnWvh7LJaTSv0kJNY1MCBLEA+DGLt4ocJUx3MIhNv8SeU9R+b7LX0VaHBMM8KhgpuYgvpD X-Received: by 2002:a17:90b:1188:b0:27b:258f:2859 with SMTP id gk8-20020a17090b118800b0027b258f2859mr1693429pjb.0.1696516393236; Thu, 05 Oct 2023 07:33:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696516393; cv=none; d=google.com; s=arc-20160816; b=rudqRVST9mDcMFoBDHjJtRh8vzpMIqnmpUUrscabbhMOPhcu2BW0f9Wq4XHgdkkqRj flj2eIOvwiNDFC2gtlMxMelUZq4IM3gGDqpnI/eu7LP9XgiZKw3P/N6TDnQHhtBmEm0U l5h4ED6En2NBYYwRM1kW2bp+r54sFOtdllBterYc9kDNWWyjLSYECk0SS7Dm16LswIcC GuU3MHlplJQtWtgVDGrCZW5mkbQFoKo2ehnOxkYZCtU4YzDu4x3AHIyWfxWMlz0O5phL bvkTlwQOEq6mrkSvcrnZ0YyiBn3UDPsQT6LujykbogsL7ciEYMe9Mg2iCk1uSTiHUze8 DL0w== 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=viMLMl5S3fhUHOnfrkj1hp6APf9+A1mUwCrJGT25R7w=; fh=taTM0Ub91m2QPo770QmKUJX9+RhaD+q65yPrlZgvRRU=; b=vtITEmcsZ+TWV4hlmUcviI3UXzVi0fsbqeqCewiR+JfrcVpR+rInVT3pLyBp2ppGrZ jj2u12gTK6ZsilN6Ng41QtmtpFxNUzwAZ8k2EPXsESN2HLi7+M6CqHcBKAKSKM/piQcL gBj46FuPOjbmpb11ANyNleY1212ePvbtatagONLIziQ2ggEcpsLOyt+Ri9zZi5c2JVKk qIFymY1U7c3BwgAe8bq2vh4fk9LT6CQHVU8LadyXoK70KLTau7TF5VVG9H/nPyFH6QsR R6eQHngu9nH37t7FeHoaK3cG7fbuXVNnzUzQRF/fcF59mOByZ3dU2+CNzPfMpxMLj9fK XHOQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=ZueOhh8j; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id d24-20020a63ed18000000b005859aec9cdcsi1530741pgi.539.2023.10.05.07.33.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Oct 2023 07:33:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=ZueOhh8j; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 04DA3832DCE7; Thu, 5 Oct 2023 07:32:55 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234791AbjJEObu (ORCPT + 99 others); Thu, 5 Oct 2023 10:31:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48734 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232295AbjJEO3j (ORCPT ); Thu, 5 Oct 2023 10:29:39 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9A13A1BD4 for ; Thu, 5 Oct 2023 06:49:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1696513798; x=1728049798; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=J5fKfUZcD1mi7ekF2HTDFpReS0ONeZjkG8dPD+kWjNs=; b=ZueOhh8jeIlnAbsNHzz1Y78bR+ot56OvwU7GYqxNMyEGZxrwg21TcXZU /YIJK+wGw5ACyeoa63zqtQLVg6cfl62Ch99/gHWBqHM0GpeTrF+ktLsaS j1N/1i01ndGAsHY9E6s8TupnqjAmhdTGHiat2xxAXrhufz7fw7blxM9oE zDdiirdPFIo7+r6X+gasVM91nxSG+qIZINb+t2rypMImXTu9naDUChzqb 5fw5SP0KLUH44ZgxwyR7LnH9/l0TvkBRtCkkqXRR+1HaRinyqLELkmeM+ tlzZUrSQmRHetBn3GcpIjCl04UcsTYDJ+OgdSj3JX40/G3f7WxpstVvIv Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10853"; a="383339411" X-IronPort-AV: E=Sophos;i="6.03,202,1694761200"; d="scan'208";a="383339411" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Oct 2023 01:16:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10853"; a="875476956" X-IronPort-AV: E=Sophos;i="6.03,202,1694761200"; d="scan'208";a="875476956" Received: from lpopiela-mobl.ger.corp.intel.com (HELO wieczorr-mobl1.intel.com) ([10.213.13.229]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Oct 2023 01:16:05 -0700 From: Maciej Wieczor-Retman To: Fenghua Yu , Reinette Chatre , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" Cc: Peter Newman , =?UTF-8?q?Ilpo=20J=C3=A4rvinen?= , linux-kernel@vger.kernel.org Subject: [PATCH v4 2/4] x86/resctrl: Enable non-contiguous CBMs in Intel CAT Date: Thu, 5 Oct 2023 10:15:37 +0200 Message-ID: X-Mailer: git-send-email 2.42.0 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Thu, 05 Oct 2023 07:32:55 -0700 (PDT) The setting for non-contiguous 1s support in Intel CAT is hardcoded to false. On these systems, writing non-contiguous 1s into the schemata file will fail before resctrl passes the value to the hardware. In Intel CAT CPUID.0x10.1:ECX[3] and CPUID.0x10.2:ECX[3] stopped being reserved and now carry information about non-contiguous 1s value support for L3 and L2 cache respectively. The CAT capacity bitmask (CBM) supports a non-contiguous 1s value if the bit is set. Replace the hardcoded non-contiguous support value with the support learned from the hardware. Add hardcoded non-contiguous support value to Haswell probe since it can't make use of CPUID for Cache allocation. Originally-by: Fenghua Yu Signed-off-by: Maciej Wieczor-Retman Tested-by: Peter Newman Reviewed-by: Ilpo Järvinen Reviewed-by: Peter Newman Reviewed-by: Reinette Chatre --- Changelog v4: - Add Ilpo's reviewed-by tag. - Add Reinette's reviewed-by tag. Changelog v3: - Add Peter's tested-by and reviewed-by tags. - Change patch subject to mention CBMs. (Babu) Changelog v2: - Rewrite part of a comment concerning Haswell. (Reinette) arch/x86/kernel/cpu/resctrl/core.c | 9 ++++++--- arch/x86/kernel/cpu/resctrl/ctrlmondata.c | 10 ++++++---- arch/x86/kernel/cpu/resctrl/internal.h | 9 +++++++++ 3 files changed, 21 insertions(+), 7 deletions(-) diff --git a/arch/x86/kernel/cpu/resctrl/core.c b/arch/x86/kernel/cpu/resctrl/core.c index c09e4fdded3c..19e0681f0435 100644 --- a/arch/x86/kernel/cpu/resctrl/core.c +++ b/arch/x86/kernel/cpu/resctrl/core.c @@ -152,6 +152,7 @@ static inline void cache_alloc_hsw_probe(void) r->cache.cbm_len = 20; r->cache.shareable_bits = 0xc0000; r->cache.min_cbm_bits = 2; + r->cache.arch_has_sparse_bitmasks = false; r->alloc_capable = true; rdt_alloc_capable = true; @@ -267,15 +268,18 @@ static void rdt_get_cache_alloc_cfg(int idx, struct rdt_resource *r) { struct rdt_hw_resource *hw_res = resctrl_to_arch_res(r); union cpuid_0x10_1_eax eax; + union cpuid_0x10_x_ecx ecx; union cpuid_0x10_x_edx edx; - u32 ebx, ecx; + u32 ebx; - cpuid_count(0x00000010, idx, &eax.full, &ebx, &ecx, &edx.full); + cpuid_count(0x00000010, idx, &eax.full, &ebx, &ecx.full, &edx.full); hw_res->num_closid = edx.split.cos_max + 1; r->cache.cbm_len = eax.split.cbm_len + 1; r->default_ctrl = BIT_MASK(eax.split.cbm_len + 1) - 1; r->cache.shareable_bits = ebx & r->default_ctrl; r->data_width = (r->cache.cbm_len + 3) / 4; + if (boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) + r->cache.arch_has_sparse_bitmasks = ecx.split.noncont; r->alloc_capable = true; } @@ -872,7 +876,6 @@ static __init void rdt_init_res_defs_intel(void) if (r->rid == RDT_RESOURCE_L3 || r->rid == RDT_RESOURCE_L2) { - r->cache.arch_has_sparse_bitmasks = false; r->cache.arch_has_per_cpu_cfg = false; r->cache.min_cbm_bits = 1; } else if (r->rid == RDT_RESOURCE_MBA) { diff --git a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c index ab45012288bb..beccb0e87ba7 100644 --- a/arch/x86/kernel/cpu/resctrl/ctrlmondata.c +++ b/arch/x86/kernel/cpu/resctrl/ctrlmondata.c @@ -87,10 +87,12 @@ int parse_bw(struct rdt_parse_data *data, struct resctrl_schema *s, /* * Check whether a cache bit mask is valid. - * For Intel the SDM says: - * Please note that all (and only) contiguous '1' combinations - * are allowed (e.g. FFFFH, 0FF0H, 003CH, etc.). - * Additionally Haswell requires at least two bits set. + * On Intel CPUs, non-contiguous 1s value support is indicated by CPUID: + * - CPUID.0x10.1:ECX[3]: L3 non-contiguous 1s value supported if 1 + * - CPUID.0x10.2:ECX[3]: L2 non-contiguous 1s value supported if 1 + * + * Haswell does not support a non-contiguous 1s value and additionally + * requires at least two bits set. * AMD allows non-contiguous bitmasks. */ static bool cbm_validate(char *buf, u32 *data, struct rdt_resource *r) diff --git a/arch/x86/kernel/cpu/resctrl/internal.h b/arch/x86/kernel/cpu/resctrl/internal.h index 85ceaf9a31ac..c47ef2f13e8e 100644 --- a/arch/x86/kernel/cpu/resctrl/internal.h +++ b/arch/x86/kernel/cpu/resctrl/internal.h @@ -492,6 +492,15 @@ union cpuid_0x10_3_eax { unsigned int full; }; +/* CPUID.(EAX=10H, ECX=ResID).ECX */ +union cpuid_0x10_x_ecx { + struct { + unsigned int reserved:3; + unsigned int noncont:1; + } split; + unsigned int full; +}; + /* CPUID.(EAX=10H, ECX=ResID).EDX */ union cpuid_0x10_x_edx { struct { -- 2.42.0