Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2423215ybm; Thu, 23 May 2019 17:09:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqxe4DTZHYvAAMATN0Yii5iNEPieDZCYLmwaOeQ5f9ykRuqQEdiUm8fOTkPTj8pv3sT0/xZi X-Received: by 2002:a17:902:8a4:: with SMTP id 33mr74654844pll.19.1558656560575; Thu, 23 May 2019 17:09:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558656560; cv=none; d=google.com; s=arc-20160816; b=Ze4TymvwahNMmkd8OAvD1tZltKLRO45yDCCBvOzyve6XgIbH6oPgpwESN48mYCcEzV ZOBkArLZQqb+Fiuv4EMtT+mfctxg9Sfosy+o6aGaHCudxCUbvjcjRavY5JtV23IEce2t Y/EfygcYmc2ImoybcDbnUc3YIRX8AeQyhf1rXd8kfHzXHA+yRAf7zKt4XSWePIWB5BUM Xy75lHgC5HdgyLVGVlZIDBeq4Pq2JiywExo12EFwebiqrtlHGpL8ALf99iQeMYlspdzx 7lEllEgfwATD1LoUZ5J35T8gtYBaYN/lZJaZlKQn9AxgmqFnQkHacb87HcDVUsBGvkw3 1kDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :ironport-sdr:ironport-sdr:dkim-signature; bh=x5hf5wUOIaMe4yaHWpncKGMFqy1JEhxkLCokw08r5TY=; b=IcCtIJRQHbw76eEVtl39dpe6Bj4iRX5OVHfjQllvJo9+6+J57ECOJEsbOCKtvggi1K Xr+IuN0uiA7/EjMgQyeMjJO+MZYO7dEOQBc+SuHc0xXMPe5u6ZeUlOS2wlidR+P1XQyK KlqSr5Ko4vfySVQRsP/WMwFeXEDpyRG0fXzmcwppakA+yp7leP4Wx08ifW8eOlrHgO4/ Dy3M7TRS0hd44xlL7emzb5/SsUjbzzHtwo7wjrBGRkd9BtrR1FLlk/KBXhi2+Dve3TQF Gk9Vwhj34pZB2z1Mq6U+E4B3x4VooGI2KX12r+TYK4O0aAXvXKHlXUuHE+Coy4PNEkXL +zpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b=obUAuUIt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=wdc.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g191si1890825pgc.197.2019.05.23.17.08.59; Thu, 23 May 2019 17:09:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b=obUAuUIt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=wdc.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388710AbfEXAHa (ORCPT + 99 others); Thu, 23 May 2019 20:07:30 -0400 Received: from esa4.hgst.iphmx.com ([216.71.154.42]:37265 "EHLO esa4.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388425AbfEXAH2 (ORCPT ); Thu, 23 May 2019 20:07:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wdc.com; i=@wdc.com; q=dns/txt; s=dkim.wdc.com; t=1558656448; x=1590192448; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=GED2GA9QcE13vUl5xR4mTzXTMt8Lm/cPPiiomsp+YVU=; b=obUAuUIt/UT9YONdGj5aAe7nyJ+5ubfBwJmKpk2zgzvAs766jbSfuTdd U7cnqDSFb+lIIeYNtIG4ps690LYLhxbcxct3xIPPbqZxWwvzAptwUfyRf xuPbGLXRMtIeigZxv5w0aioB0zWpZfngmSKVRZwHrUhNmsp4uYWpzxmOM AAkxCm9n3eioKsw3hWjBoBhyGa6cMuGfJ33aa3zAgTOwwzSVu52mhP9OO GJqcTUUAMutt9qKBipVkU3a7eKJOhsVw45L3X3h4g0GlTi3Dk/JJs5ehL Vdpeb4b8cgYwAJvvtv6LK2an2sPMS5vc0T/DMFoo7NHiG4CqfBV5iRSeV Q==; X-IronPort-AV: E=Sophos;i="5.60,505,1549900800"; d="scan'208";a="108976452" Received: from h199-255-45-15.hgst.com (HELO uls-op-cesaep02.wdc.com) ([199.255.45.15]) by ob1.hgst.iphmx.com with ESMTP; 24 May 2019 08:07:26 +0800 IronPort-SDR: 7dYyZsuQPTbahR8Po1JuSt2YcSX3mvzPDX7V5YenpeSuXcDH3IcCa6zM/knzcYeFUnj9NwbVvu RVIdJ7iDGh8FVJuzkZ8FFraqHLQ378vChaYfbzcWApQHt0OJ83SA1U15hhKrV+akEX7ekCjjPA Tll/Bk7jXRPkYPRLKfeqdV0UX8hd1OP4lkTXmYYp/vVtFGVLwAzGAgo87zKPENGXAlEhbHluai Lt2U3R7UaAZyNsFdXMCRtelyDI2sP0n7zdhMqkALBTJ56VG3qGBpWJetlbFrhfLgTkQtTHSGMs Sw2irdHsNWs8+g3eEmlqKd1K Received: from uls-op-cesaip02.wdc.com ([10.248.3.37]) by uls-op-cesaep02.wdc.com with ESMTP; 23 May 2019 16:45:08 -0700 IronPort-SDR: 341jEcSs6pSCjQ27H/KQc3ZHyavI69B6lqsdo28+lkRjZYQlZhRKYL6fFHFnMqSkPyjC2YpFjN zgf5XrjEEjr8QBjGGvG/0WiRgUIkA5iz8PX4gzAfQfnrfLobcPvqyxh88Fr+aWw08EN4duinZA dJFRPpcTHeyc31oDWsGsAXy71D7XdUkLHJjHUOyGTxH2Xh+EsBD7biDVoZpWsOaOoMwVsWGTY/ F3mUzmQiap9ZbpO05xrow58G5i4810s27v9u9q9+PMc7WJdNlSpQNtGGQrPnl/RT9bVMZu4Qdj xyg= Received: from jedi-01.sdcorp.global.sandisk.com (HELO jedi-01.int.fusionio.com) ([10.11.143.218]) by uls-op-cesaip02.wdc.com with ESMTP; 23 May 2019 17:07:26 -0700 From: Atish Patra To: linux-kernel@vger.kernel.org Cc: Sudeep Holla , Rob Herring , Albert Ou , Andreas Schwab , Anup Patel , Atish Patra , Catalin Marinas , devicetree@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Jeremy Linton , linux-riscv@lists.infradead.org, Mark Rutland , Morten Rasmussen , Otto Sabart , Palmer Dabbelt , Paul Walmsley , "Peter Zijlstra (Intel)" , "Rafael J. Wysocki" , Rob Herring , Thomas Gleixner , Will Deacon , linux-arm-kernel@lists.infradead.org Subject: [RFT PATCH v5 1/5] Documentation: DT: arm: add support for sockets defining package boundaries Date: Thu, 23 May 2019 17:06:48 -0700 Message-Id: <20190524000653.13005-2-atish.patra@wdc.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190524000653.13005-1-atish.patra@wdc.com> References: <20190524000653.13005-1-atish.patra@wdc.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Sudeep Holla The current ARM DT topology description provides the operating system with a topological view of the system that is based on leaf nodes representing either cores or threads (in an SMT system) and a hierarchical set of cluster nodes that creates a hierarchical topology view of how those cores and threads are grouped. However this hierarchical representation of clusters does not allow to describe what topology level actually represents the physical package or the socket boundary, which is a key piece of information to be used by an operating system to optimize resource allocation and scheduling. Lets add a new "socket" node type in the cpu-map node to describe the same. Signed-off-by: Sudeep Holla Reviewed-by: Rob Herring --- .../devicetree/bindings/arm/topology.txt | 52 ++++++++++++++----- 1 file changed, 39 insertions(+), 13 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/topology.txt b/Documentation/devicetree/bindings/arm/topology.txt index b0d80c0fb265..3b8febb46dad 100644 --- a/Documentation/devicetree/bindings/arm/topology.txt +++ b/Documentation/devicetree/bindings/arm/topology.txt @@ -9,6 +9,7 @@ ARM topology binding description In an ARM system, the hierarchy of CPUs is defined through three entities that are used to describe the layout of physical CPUs in the system: +- socket - cluster - core - thread @@ -63,21 +64,23 @@ nodes are listed. The cpu-map node's child nodes can be: - - one or more cluster nodes + - one or more cluster nodes or + - one or more socket nodes in a multi-socket system Any other configuration is considered invalid. -The cpu-map node can only contain three types of child nodes: +The cpu-map node can only contain 4 types of child nodes: +- socket node - cluster node - core node - thread node whose bindings are described in paragraph 3. -The nodes describing the CPU topology (cluster/core/thread) can only -be defined within the cpu-map node and every core/thread in the system -must be defined within the topology. Any other configuration is +The nodes describing the CPU topology (socket/cluster/core/thread) can +only be defined within the cpu-map node and every core/thread in the +system must be defined within the topology. Any other configuration is invalid and therefore must be ignored. =========================================== @@ -85,26 +88,44 @@ invalid and therefore must be ignored. =========================================== cpu-map child nodes must follow a naming convention where the node name -must be "clusterN", "coreN", "threadN" depending on the node type (ie -cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes which -are siblings within a single common parent node must be given a unique and +must be "socketN", "clusterN", "coreN", "threadN" depending on the node type +(ie socket/cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes +which are siblings within a single common parent node must be given a unique and sequential N value, starting from 0). cpu-map child nodes which do not share a common parent node can have the same name (ie same number N as other cpu-map child nodes at different device tree levels) since name uniqueness will be guaranteed by the device tree hierarchy. =========================================== -3 - cluster/core/thread node bindings +3 - socket/cluster/core/thread node bindings =========================================== -Bindings for cluster/cpu/thread nodes are defined as follows: +Bindings for socket/cluster/cpu/thread nodes are defined as follows: + +- socket node + + Description: must be declared within a cpu-map node, one node + per physical socket in the system. A system can + contain single or multiple physical socket. + The association of sockets and NUMA nodes is beyond + the scope of this bindings, please refer [2] for + NUMA bindings. + + This node is optional for a single socket system. + + The socket node name must be "socketN" as described in 2.1 above. + A socket node can not be a leaf node. + + A socket node's child nodes must be one or more cluster nodes. + + Any other configuration is considered invalid. - cluster node Description: must be declared within a cpu-map node, one node per cluster. A system can contain several layers of - clustering and cluster nodes can be contained in parent - cluster nodes. + clustering within a single physical socket and cluster + nodes can be contained in parent cluster nodes. The cluster node name must be "clusterN" as described in 2.1 above. A cluster node can not be a leaf node. @@ -164,13 +185,15 @@ Bindings for cluster/cpu/thread nodes are defined as follows: 4 - Example dts =========================================== -Example 1 (ARM 64-bit, 16-cpu system, two clusters of clusters): +Example 1 (ARM 64-bit, 16-cpu system, two clusters of clusters in a single +physical socket): cpus { #size-cells = <0>; #address-cells = <2>; cpu-map { + socket0 { cluster0 { cluster0 { core0 { @@ -253,6 +276,7 @@ cpus { }; }; }; + }; CPU0: cpu@0 { device_type = "cpu"; @@ -473,3 +497,5 @@ cpus { =============================================================================== [1] ARM Linux kernel documentation Documentation/devicetree/bindings/arm/cpus.yaml +[2] Devicetree NUMA binding description + Documentation/devicetree/bindings/numa.txt -- 2.21.0