Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2469525ybd; Thu, 27 Jun 2019 12:56:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqyTJTxjzjeYhyzhWVbrl8Z+DZyALs60mT36wqne2brVNeAe/KxEFsUAbyooWvZDDC5nvL9m X-Received: by 2002:a17:90a:8985:: with SMTP id v5mr8055997pjn.136.1561665411487; Thu, 27 Jun 2019 12:56:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561665411; cv=none; d=google.com; s=arc-20160816; b=lFm6k7hlMIh2ix/R5rNRrMHPO1a3cR5KhiNrS+sh/6osi0RY1nyg3c9uwPiyNXnaAr hiiCbbBMJxd/YVe6yOdOb23By0QWsu3pxXxAIoOo3NCZq7DPJjU69IrGunyjHxjH1WV6 k7pdUOJ/eNiZcucd2eOwVMeOwMz3ocRV/qW6awjuZMowu0VEJJYzw3Y/xrhB506F+1Cx 7Yxi8lYv1gknLwleOhEBEtQiPo8CKR4a7ynezIhRcbZa6biYUY6H4cimkPMHJMlvHSNf lLb/ewjuSP7zjTjGV03CVTDnt5iszleJ6pJhNt0cjF17z/5zsD++cXLsZ24U8lVDyyvI DjGA== 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 :message-id:date:subject:cc:to:from:ironport-sdr:ironport-sdr :dkim-signature; bh=jzapr4diE8Zho4YrAt6eWJ20RwcRcSaKPtLh5cMevdQ=; b=ZiODZ/ebB3IEG3ysUdcZSzZzKtod+e+tEXX3+kamZNwKLknxjbFwlzRngOkDjfG/d0 bEIuqR7dDckaR9+96HlXUk6dm1SJrkhJNJY05Zg7/qsKwYXXJbjOzKLlbXtJnavofZ5g m6O0cyQ9Z/8i9uTVfhg/pPvQkvxOCnYiz/sN3ZWrDTkoxQAtfLuptdaMq4TSZrtP8jJM qhXpl/UzXHLYGYA7cYF+aTxJcioWyMTs3sCmy3GD4p/7I17QACcq00/gCBiPXCmYhN5g dCAeP1fmwLF/EPSfAydZeZJ4w3lSGj7Aw1Qo6z6DeHwMLfQhSXlfl1LKf2FORQXlI4cy ugNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b=hHQuEBik; 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 r71si5609pgr.518.2019.06.27.12.56.35; Thu, 27 Jun 2019 12:56:51 -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=hHQuEBik; 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 S1726531AbfF0TzZ (ORCPT + 99 others); Thu, 27 Jun 2019 15:55:25 -0400 Received: from esa5.hgst.iphmx.com ([216.71.153.144]:23412 "EHLO esa5.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726384AbfF0TzY (ORCPT ); Thu, 27 Jun 2019 15:55:24 -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=1561665324; x=1593201324; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=OBRreVPl8/1uZ8733sksixlMzFip9pXYBiHmIUFSRKk=; b=hHQuEBikoDVNqYu5S9ImCiCDXG+j0zA2JJ61G8AOFezRlbrlF7pa44Hc E3lFe3+pVATKkWNjCcB8dyT8Njud1/0DQjgJAhnSG35i3Y+6DlwDI3qU0 U3+VKVfb0ZTDr8JIQl83foL7Vqyjg/P5x1TjHQC70MUB/QIfxBn/fXvjA upQ+4HFg6cncgMyRlVPnNWFnIr/obvYHX8FxNKTw+F+/E9McrOlNZ4tHg 5XkI4fdCybwpJSf88+YRfugvYC+GZ47F8MjVkxE8JiiJLRkEtHk/W1bfK RpSH/YCioKe9qPhnBvw2dAie8cCbUF0n9ODKMGsZyLIcM1+TjEgIlEe2m w==; X-IronPort-AV: E=Sophos;i="5.63,424,1557158400"; d="scan'208";a="112927430" 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; 28 Jun 2019 03:55:24 +0800 IronPort-SDR: mJ0v9LQzpOE575mcO+Uky+5JQpAmy1umCE8ica4I+p/BgVI84fXfKvtw760Cm1Li7dt3bNdDKE UPjW9pa9wIqz1xu+zCEl5NNw9+gAirnftykAN+hUjfKyxdiQqluiv2zpxv+CCbOkB2rcaSJMwI 6P+5LWC8X79LjV0JMSlyDHxhA0VWi1PxVw2H60W7QIEI9DwWNnLMD0PVtZZ9ZaJfiRQ6eGtzRv DsaXKTGOgYeTQrhUK0lpdztKXvLxdFY2UWHFxtAAEUTXnEd7J+JDfR+Vmy0daWP6zz39gUZxde XDnKf1vNxyz9beStapibOaUJ Received: from uls-op-cesaip01.wdc.com ([10.248.3.36]) by uls-op-cesaep02.wdc.com with ESMTP; 27 Jun 2019 12:54:37 -0700 IronPort-SDR: QZfOZnobUoIlq7QA0oz41TT5jgDsxp1aB5nnN69VvT8K1DSzCnndUMF1HY+s5RqvAZhZkmY3GM VeO1OT8mI7wZ8eNBVoevsc8J4zeiVtbeP4YuEDFs+vyzRxulRFVm1xKLfyFoRel7EPkrWt+r1s Gr0RKX4GZwvu7o3r8YE903nVlo7x9/xuzE48qkgcppHDtM5y4R0iEBPW36hKiSlJqf1vmAMgdo Tu3PwJnlsUqC3/ImjypBeOVyoY6LLqCMolukiGhrI2NsOAFHrEkRr5N9Y2Jfrq/x/bt30aPhzA EzI= Received: from jedi-01.sdcorp.global.sandisk.com (HELO jedi-01.int.fusionio.com) ([10.11.143.218]) by uls-op-cesaip01.wdc.com with ESMTP; 27 Jun 2019 12:55:23 -0700 From: Atish Patra To: linux-kernel@vger.kernel.org Cc: Atish Patra , Jeremy Linton , Albert Ou , Anup Patel , Catalin Marinas , "David S. Miller" , devicetree@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Johan Hovold , Linus Walleij , linux-riscv@lists.infradead.org, Mark Rutland , Mauro Carvalho Chehab , Morten Rasmussen , Otto Sabart , Palmer Dabbelt , Paul Walmsley , "Peter Zijlstra (Intel)" , "Rafael J. Wysocki" , Rob Herring , Sudeep Holla , Thomas Gleixner , Will Deacon , Will Deacon , linux-arm-kernel@lists.infradead.org, Russell King Subject: [PATCH v8 0/7] Unify CPU topology across ARM & RISC-V Date: Thu, 27 Jun 2019 12:52:55 -0700 Message-Id: <20190627195302.28300-1-atish.patra@wdc.com> X-Mailer: git-send-email 2.21.0 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 The cpu-map DT entry in ARM can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent its own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be moved to a common location so that RISC-V or any other architecture can leverage that. The relevant discussion regarding unifying cpu topology can be found in [1]. arch_topology seems to be a perfect place to move the common code. I have not introduced any significant functional changes in the moved code. The only downside in this approach is that the capacity code will be executed for RISC-V as well. But, it will exit immediately after not able to find the appropriate DT node. If the overhead is considered too much, we can always compile out capacity related functions under a different config for the architectures that do not support them. There was an opportunity to unify topology data structure for ARM32 done by patch 3/4. But, I refrained from making any other changes as I am not very well versed with original intention for some functions that are present in arch_topology.c. I hope this patch series can be served as a baseline for such changes in the future. The patches have been tested for RISC-V, ARM64, ARM32 & compile tested for x86. From Jeremy, "I applied these to 5.2rc2, along with my PPTT/MT change and verified the system & scheduler topology/etc on DAWN and ThunderX2 using ACPI on arm64. They appear to be working correctly. so for the series, Tested-by: Jeremy Linton " The socket change[2] is also now part of this series. [1] https://lkml.org/lkml/2018/11/6/19 [2] https://lkml.org/lkml/2018/11/7/918 This patch series can also be found at https://github.com/atishp04/linux/tree/5.2-rc6_topology QEMU changes for RISC-V topology are available here https://lists.nongnu.org/archive/html/qemu-devel/2019-06/msg05974.html HiFive Unleashed DT with topology node is available here. https://patchwork.kernel.org/patch/11014313/ Changes from v7->v8 1. Regenerated the patch series without -b option in git format-patch. Without that, git apply from email won't work because ignored space changes. Changes from v6->v7 1. Added socket to HiFive Unleashed topology example. 2. Added Acked-by & Reviewed-by. Changes from v5->v6 1. Added two more patches from Sudeep about maintainership of arch_topology.c and Kconfig update. 2. Added Tested-by & Reviewed-by 3. Fixed a nit (reordering of variables) Changes from v4-v5 1. Removed the arch_topology.h header inclusion from topology.c and arch_topology.c file. Added it in linux/topology.h. 2. core_id is set to -1 upon reset. Otherwise, ARM topology store function does not work. Changes from v3->v4 1. Get rid of ARM32 specific information in topology structure. 2. Remove redundant functions from ARM32 and use common code instead. Changes from v2->v3 1. Cover letter update with experiment DT for topology changes. 2. Added the patch for [2]. Changes from v1->v2 1. ARM32 can now use the common code as well. Atish Patra (4): dt-binding: cpu-topology: Move cpu-map to a common binding. cpu-topology: Move cpu topology code to common code. arm: Use common cpu_topology structure and functions. RISC-V: Parse cpu topology during boot. Sudeep Holla (3): Documentation: DT: arm: add support for sockets defining package boundaries base: arch_topology: update Kconfig help description MAINTAINERS: Add an entry for generic architecture topology .../topology.txt => cpu/cpu-topology.txt} | 256 ++++++++++----- MAINTAINERS | 7 + arch/arm/include/asm/topology.h | 20 -- arch/arm/kernel/topology.c | 60 +--- arch/arm64/include/asm/topology.h | 23 -- arch/arm64/kernel/topology.c | 303 +----------------- arch/riscv/Kconfig | 1 + arch/riscv/kernel/smpboot.c | 3 + drivers/base/Kconfig | 2 +- drivers/base/arch_topology.c | 298 +++++++++++++++++ include/linux/arch_topology.h | 26 ++ include/linux/topology.h | 1 + 12 files changed, 514 insertions(+), 486 deletions(-) rename Documentation/devicetree/bindings/{arm/topology.txt => cpu/cpu-topology.txt} (66%) -- 2.21.0