Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp72588rwl; Thu, 6 Apr 2023 13:23:41 -0700 (PDT) X-Google-Smtp-Source: AKy350adSq62ewqI6C0+Gczz0QqItII+1egJxRaCKEE0xil9tQEUkmpM2fJjPyYY1zPTzswmZDhs X-Received: by 2002:a17:906:dfed:b0:931:df8d:113 with SMTP id lc13-20020a170906dfed00b00931df8d0113mr175521ejc.26.1680812621128; Thu, 06 Apr 2023 13:23:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680812621; cv=none; d=google.com; s=arc-20160816; b=diKW8x3XJhA+0CCY0P6ERTn+ut2vu9+hT516zTzG1jwiRfib/ChspigrFGPeE1YjbK 4Xa3sc6BWPYYEwLP6nJnsYHsxCeI6prHH/FEfpg9mMu95rvYZe6xbqXGR6RhK5qjTJB0 z3OEu2+EahO0u1AKU6YdXvXc8s+h9HUYrynKHkOGO9qMhQGwNLIIrwrLPhEHJmaRiKv/ rletTqZ/d7P+vl4aIjD1J39iD2Tkrxk3JP+Icgw5QtAkhdndj1zJeInB8GAf0yqp1EaN No4+1qYgtcP+o6+7qE8KiNnCkP5WD34g7NU5TrOnmRrqjPLELzyetN7mhOMRtg+4xjsE hsgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from:dkim-signature; bh=NTBBj/KKQ6lD+ULH/KI6U3c81SKNcUdBRzxIvPYFOMc=; b=enPrbtAi8ShN8hAXkk3c7rwNK+QJy1SX5V9ZpG4X9ytTg+Llwcmg4xUy+UGcXRBtzY Qc0x0JnZ9ibUlSiqoHTjwuhJtLd2DeuwtQ6dM4x6SDHxMxoLFXfNO1qpMmGIQTaBQAB9 5gM38rFbczoLRGRul7u0iInFDHPIMIy9w4yohKyu9fCfG55GZWb/6DAhYB9fs6AFtYFB K7F2FeoMoMPZio6f4gUnzobsbW21fh7TDwizNYF4MkBzJ3tpvX+yydRN1Fite8mv+0Vb 3C8t7oTw32eV1O8Z4iowqYwTgjsZNBRxMsLPrGOTlmLKNa8zDHFVBVzblMhVSb5CkWlo BX/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=N6rjBtfx; 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=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l10-20020aa7c3ca000000b005002cb238e1si1980566edr.350.2023.04.06.13.23.14; Thu, 06 Apr 2023 13:23:41 -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; dkim=pass header.i=@intel.com header.s=Intel header.b=N6rjBtfx; 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=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239188AbjDFUV0 (ORCPT + 99 others); Thu, 6 Apr 2023 16:21:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238977AbjDFUVE (ORCPT ); Thu, 6 Apr 2023 16:21:04 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E9D1993E4 for ; Thu, 6 Apr 2023 13:21:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680812462; x=1712348462; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=7BReSg2zsB5y0pHQ7AAJ8Y7mGqv5oVtV05dcWb8L9Pw=; b=N6rjBtfx65jWcCQmdQg2ssaKQfkguwVN4wsZi4TXcALhVZtpef6g+FVp iLebNQ2VJHiC2/Q9AuySYVZKTMRfpbhxQpFQU+sKPIg3NzJBX3DQHal2U BY2bpMOLc+ccxhbqUANIZvKWK0pmTEanH8Uj9VafZRymRshds2gSs/PjW kHPIe/rgjAWtySDEj5Q2Rwmc+VffbaFxceR2MTqKQgWRBQUipmAECz5jT T4Oy7q9KssoFsoVy4hoU81gtN/EwYoYB6B32SA4JATRd+AZxdJfYe0WcK 9C0GhEQ2geELryEYBDauu2HO+1tTIH8wKRcAF5A+efuwetvozuF3Zpg+e A==; X-IronPort-AV: E=McAfee;i="6600,9927,10672"; a="407957793" X-IronPort-AV: E=Sophos;i="5.98,323,1673942400"; d="scan'208";a="407957793" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Apr 2023 13:21:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10672"; a="861529894" X-IronPort-AV: E=Sophos;i="5.98,323,1673942400"; d="scan'208";a="861529894" Received: from ranerica-svr.sc.intel.com ([172.25.110.23]) by orsmga005.jf.intel.com with ESMTP; 06 Apr 2023 13:21:01 -0700 From: Ricardo Neri To: "Peter Zijlstra (Intel)" , Juri Lelli , Vincent Guittot Cc: Ricardo Neri , "Ravi V. Shankar" , Ben Segall , Daniel Bristot de Oliveira , Dietmar Eggemann , Len Brown , Mel Gorman , "Rafael J. Wysocki" , Srinivas Pandruvada , Steven Rostedt , Tim Chen , Valentin Schneider , Ionela Voinescu , x86@kernel.org, linux-kernel@vger.kernel.org, Ricardo Neri , "Tim C . Chen" Subject: [PATCH v4 09/12] sched/topology: Remove SHARED_CHILD from ASYM_PACKING Date: Thu, 6 Apr 2023 13:31:45 -0700 Message-Id: <20230406203148.19182-10-ricardo.neri-calderon@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20230406203148.19182-1-ricardo.neri-calderon@linux.intel.com> References: <20230406203148.19182-1-ricardo.neri-calderon@linux.intel.com> X-Spam-Status: No, score=-2.4 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_NONE 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 Only x86 and Power7 use ASYM_PACKING. They use it differently. Power7 has cores of equal priority, but the SMT siblings of a core have different priorities. Parent scheduling domains do not need (nor have) the ASYM_PACKING flag. SHARED_CHILD is not needed. Using SHARED_PARENT would cause the topology debug code to complain. X86 has cores of different priority, but all the SMT siblings of the core have equal priority. It needs ASYM_PACKING at the MC level, but not at the SMT level (it also needs it at upper levels if they have scheduling groups of different priority). Removing ASYM_PACKING from the SMT domain causes the topology debug code to complain. Remove SHARED_CHILD for now. We still need a topology check that satisfies both architectures. Cc: Ben Segall Cc: Daniel Bristot de Oliveira Cc: Dietmar Eggemann Cc: Ionela Voinescu Cc: Len Brown Cc: Mel Gorman Cc: Rafael J. Wysocki Cc: Srinivas Pandruvada Cc: Steven Rostedt Cc: Tim C. Chen Cc: Valentin Schneider Cc: x86@kernel.org Cc: linux-kernel@vger.kernel.org Tested-by: Zhang Rui Suggested-by: Valentin Schneider Signed-off-by: Ricardo Neri --- Changes since v3: * Removed spurious space. Changes since v2: * Introduced this patch. Changes since v1: * N/A --- include/linux/sched/sd_flags.h | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/include/linux/sched/sd_flags.h b/include/linux/sched/sd_flags.h index 57bde66d95f7..fad77b5172e2 100644 --- a/include/linux/sched/sd_flags.h +++ b/include/linux/sched/sd_flags.h @@ -132,12 +132,9 @@ SD_FLAG(SD_SERIALIZE, SDF_SHARED_PARENT | SDF_NEEDS_GROUPS) /* * Place busy tasks earlier in the domain * - * SHARED_CHILD: Usually set on the SMT level. Technically could be set further - * up, but currently assumed to be set from the base domain - * upwards (see update_top_cache_domain()). * NEEDS_GROUPS: Load balancing flag. */ -SD_FLAG(SD_ASYM_PACKING, SDF_SHARED_CHILD | SDF_NEEDS_GROUPS) +SD_FLAG(SD_ASYM_PACKING, SDF_NEEDS_GROUPS) /* * Prefer to place tasks in a sibling domain -- 2.25.1