From patchwork Sun Apr 28 00:25:25 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Atish Patra X-Patchwork-Id: 162997 Delivered-To: patch@linaro.org Received: by 2002:a92:7e86:0:0:0:0:0 with SMTP id q6csp291972ill; Sat, 27 Apr 2019 17:26:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqzOEMyr0cR1CPDLFU29s/8V5Ij+SRFgSBPP1g1sZGr8nzfNnfZNbCB2+9r0UHK98DiRsg/K X-Received: by 2002:a62:4852:: with SMTP id v79mr55279597pfa.72.1556411177931; Sat, 27 Apr 2019 17:26:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556411177; cv=none; d=google.com; s=arc-20160816; b=ai1v217Xdf6M+B+J/DtYuSfUvpq1oW9pEq9NniPPRjNV6aKurUJs0hH6LKl3Exq09v CNvlee7kkT9m7GXtZHM6SezCYPVCK2u2r4719QG4Wte0WRUfCp4oFZZ+LVT7WgwOKa+q RkPGA+BnlAq1Fpq8lf7BL1hTX3cGaEYZ/7RLdNzRoHYnKUb1xsdQF90P+g8alaUop/a0 dd0q1Qj53nuHiJgH2BqrsfvSbvz3WPt21R3nld3secrguTLMFfNpgCL/fgdqRaRjK8nG eqknIEcbrTTp58o4zah4eRZEuH5N9MVy3Bs73phI2i9FTXT3SQ8HqE0h2Qq7jKgTuk4K z9GA== 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=qdulT++MsJb4OW0Io5bcwtFUZQPKI/zf1frbwq5MFdjhuqPJ/xnwcqBDveFiHEooLm PP08KspvSUqI5r9nEvtkCRr23+bl/iQId97F6oo9/qgw90NvF8MIdz2hkQ/iirpKwdqZ 5Wew3UpKUVsqy/dlMmnBcH3PbHJl5NrlmaMarRDbMJQu1mTZjxgYK/SNCyc6BTfILG2g JVizOGHTY4GaACbJr1h9xCFtxwJOjO1WQbOVsPaWt+FDMCix9GSMnaaiPUoHdeiPFiYL 7runGxG9cwfVua3h2S3Ssf3CUw/wfqTUClLSiRVscWTz73yiO+ri0DvescjjcrnYSdDO WVTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b=nLUGjWtQ; 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 h3si21464717pgc.299.2019.04.27.17.26.17; Sat, 27 Apr 2019 17:26:17 -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=nLUGjWtQ; 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 S1726380AbfD1A0F (ORCPT + 30 others); Sat, 27 Apr 2019 20:26:05 -0400 Received: from esa4.hgst.iphmx.com ([216.71.154.42]:14541 "EHLO esa4.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726123AbfD1A0D (ORCPT ); Sat, 27 Apr 2019 20:26:03 -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=1556411163; x=1587947163; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=GED2GA9QcE13vUl5xR4mTzXTMt8Lm/cPPiiomsp+YVU=; b=nLUGjWtQqowi97lseqUAhswir/0z/AcASYoIP2UHB2LmMnhk1PGVGcjz nn7CeoFSvQp3lgEs6F6AhDQbBLYhfbMsOJ2YIo3I97Y314clwt7zFumSt tgF6CU/ijI8vuEBRh2vAMw3QLr0f/k/ZZC+HjzkK0nSsxo4thMl4wiy77 tyIgldq5khJAeLzt9DSGszUFJzPfPVZNNm9oBO7MtrkgfqUCEdoz/OFR5 7yiDI410jjOSrMk628/3SgayHIsT73SAVRauXX/fZIJmesGQ6gwly14Z2 J3fiP99tY/rmCD+mXLfD1HN2oBGAE5YdlznCIF50y7BJCUStM3nHc/e/Z w==; X-IronPort-AV: E=Sophos;i="5.60,403,1549900800"; d="scan'208";a="106993911" Received: from uls-op-cesaip02.wdc.com (HELO uls-op-cesaep02.wdc.com) ([199.255.45.15]) by ob1.hgst.iphmx.com with ESMTP; 28 Apr 2019 08:26:02 +0800 IronPort-SDR: lALaY9LvY+UoL2jQGKSfJbDBcRQl3Cl5FWbts7HvrLhS47MgocbGX1ZnBR3bz0eD5asal5cLSg 7AgrwkMsCAfwITQyvRblZ1HUofd0V/zYfmmubFP5dvZXiWlPNsAN/od+o8gFGON0UU0SUEPlBd O0BFyh1KB8mPgjyBv7RI63W/qOAFRgFz3WXhzlLsbIE/kxddzXvXGNfTAKtLD4gjxSrG2VaCmA aAfCB81xQb8BO8P88u2fqvvmUyuUJGq6bVzwMJEUCWRrztSpbqRde3rX9Rj5n/WO3E6baqdFmi 3wKYOUWVgmJVNQjUuMOtSORA Received: from uls-op-cesaip02.wdc.com ([10.248.3.37]) by uls-op-cesaep02.wdc.com with ESMTP; 27 Apr 2019 17:04:36 -0700 IronPort-SDR: CuFz6aOs3VJ5FTmEp5r2s36iLfyWFzX6NF4F6tZhzK27NPdWHulWD8iQXjEiADaV9yFjk6hYUy +VkvWOndipzbrhAyNsPXeDIw3vobW3I8yqwEH7byyFUCxuIB1JBxocOSNmNBxKIy2v2ONoxnlN qvN6fOSgtF+K0k4G0gFm8eSJjWATALJusDDOX78cRyCtRyrWmCdWNDu4heFXBVSIQkK/oGVKSQ FmAVVEVV51AXXfL6nX/Zpgn0bAN9Xr1Vd7XoQNsmaRosrvwp/L3gGJz8JX+si5Ql2xmHKiqhKS LSI= 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; 27 Apr 2019 17:26:02 -0700 From: Atish Patra To: linux-kernel@vger.kernel.org Cc: Sudeep Holla , Rob Herring , Albert Ou , Andreas Schwab , Anup Patel , Ard Biesheuvel , 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 v4 1/5] Documentation: DT: arm: add support for sockets defining package boundaries Date: Sat, 27 Apr 2019 17:25:25 -0700 Message-Id: <20190428002529.14229-2-atish.patra@wdc.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190428002529.14229-1-atish.patra@wdc.com> References: <20190428002529.14229-1-atish.patra@wdc.com> MIME-Version: 1.0 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(-) -- 2.21.0 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