Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2882253ybi; Mon, 17 Jun 2019 12:01:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqy/KARW/jDpYFb6dXH1mRHRhjOziLnzFWhsMJ0Hd4BQ7ej4JuAB7s+mNYqjaPH1eergqwvY X-Received: by 2002:aa7:8dcc:: with SMTP id j12mr50082944pfr.137.1560798090601; Mon, 17 Jun 2019 12:01:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560798090; cv=none; d=google.com; s=arc-20160816; b=QLxrmgYUJz1dY6/Hxuar8Y9Senr6s+QnwcMSFHQTMbvbuEUXxv1VTxLuVdtVwajWS2 xJtgEkrgWG7w4VOpCO3RzfEG04EjCHXXaSRbgS2wD4o76T7Q73ia3Um2j2Sp33+EKM2L 6AhhwAP6gDoyM8Oz8XFfDuybAe63K6EMrFkkk97zD21iBfYc2hIwnSUyFQ1hF3bx5QBf YAEdpohMxsPD17TCa6Z1L/wwr2cm5B1emPcFx4lQFpvk+eeVAmQaGrHbF2cHCyKAyib6 UDjuV3LaRhdOEgAoiOtVsajA7t8dgIMsbbBp/EOrYJ+jKcNPbjjp8YZtXTlGHprgcreI 7jHA== 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=yzvZVc2CvfgBb1QTg11y2tIy6GN1U30qPyxCRV56oEw=; b=g5Cc457Ip3mgOV9/uWmYneQqvnpKoanRQYeti9bI1rPlMsOnbKlYyTxtA9sCZ/fM9+ fI7KiCDnTsRI7d8JaE3b7EWxSjEP8I7aj0z14zLmJ/HT9sXAXL7TQOJiqjNqPZQ3Izf7 AN3yeYdpgQAoAaJVVTyZAN8l6jQChAUPl6GsFLaTEsIUTdR+tMl/9MxNzgu8DS5zU8hV 2KVg4IIIIFbbpJCoCMgTLBbQe8Ult+6wmzEAvZeyLd14Pm7RlO/XwRLYpb7qaCzNZwuV j3ZqX1v+QNJlfROmDmwb5AWwmoIbRWZr8KlIFZj0LNXmzg/rDYYRQ7yAYRJM+qfT7yyS XWBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b=CzJrQzOb; 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 a19si7540604pgm.434.2019.06.17.12.01.15; Mon, 17 Jun 2019 12:01:30 -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=CzJrQzOb; 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 S1726585AbfFQS75 (ORCPT + 99 others); Mon, 17 Jun 2019 14:59:57 -0400 Received: from esa5.hgst.iphmx.com ([216.71.153.144]:25677 "EHLO esa5.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbfFQS75 (ORCPT ); Mon, 17 Jun 2019 14:59:57 -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=1560797996; x=1592333996; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=4gsxyypkDkZeEPMfmtQxEkRSX1iwXhYxZdPR6g9XGVc=; b=CzJrQzObXbCHVNeEG/EumriZAV49J5zvn3IRs8I1+dIai0lHrq4eNXqU ThNE/rn+0ZYZznnoVks+Aw0LGZ+7VVB1VLWRHSmoByo7pgCBpFXgZ2zgz g3qbBSydk5sBWC0MQgf6S5kMNQOQuc8lF4X14Mf4obAKNeMujfewVk8lV r724a71EoySc5NunfxDmq6gOGVDDwgyC3GYKZ66ZXsRrkhhMnVGsgcXSj qMKDUobV+JSn8eHrOQaqmt81O2qUU1kpFCXj2COeQNAyt56IVYcCJM7kf LC3Lllxgm4llfeslHqzmdZGgfjJHfUme3FwLbmnxJMvc6SG/iZOT6q69p g==; X-IronPort-AV: E=Sophos;i="5.63,386,1557158400"; d="scan'208";a="112032229" Received: from uls-op-cesaip02.wdc.com (HELO uls-op-cesaep02.wdc.com) ([199.255.45.15]) by ob1.hgst.iphmx.com with ESMTP; 18 Jun 2019 02:59:56 +0800 IronPort-SDR: 1/LZhrq/7GoyNXzB/i0oJ49yqDqcT3eLditczXWuT2TGU/4tmci5bG9iKnnRTAftYYktOjtW7Z jkt+MO5ROApJ7YMbNhrhPquSFlDiZC3E7DwvKms66HjHBuxTmuYXZGGMw6AiwJSLQL2zfnsVGy YfmJ2UaOSp+7Wc2rLag0K6HTm/ND6KCTKjg/zAKwLrWYiXvN0o9ZYczDHNhSRZI03v04lgbI4r gl2QP8uAltIb4enEHvzGHDhY7umEDjXu++z28W0gKr0WofvdrG58tlpORW+Onyr7rApF2E8yKL x+2ApQBeK0K6h3uSmIe+fldy Received: from uls-op-cesaip01.wdc.com ([10.248.3.36]) by uls-op-cesaep02.wdc.com with ESMTP; 17 Jun 2019 11:59:26 -0700 IronPort-SDR: rf9zdZSYllUoDZSjIGKlJyFrk3+jHCW0uMuhJDcO3oUablZz06zS5vUYxDAc1e5wHt0RVBa1Yj vpJC9lvyV0577zFg84pDpuJ4wLIPPVz9YQY5yIAdeGL7rU3pOU80+hl6B4jfSVaHG3H8svdDMg ROnzXWVSVLq7HPYqWwNVwVHbXwHziHw5B0DydW3hbiCAT+C+dnKVqqthxRyUKywWtqHTgHB8bb lrs3Rjkz9SwyIjaR4F6FZyLZSlm0I1/K9xL+82zj/gud4kvW0R7yiaiLVQ/XaOzNxTMue+7nE/ /OQ= 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; 17 Jun 2019 11:59:54 -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 , Jonathan Cameron , 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" , Richard Fontana , Rob Herring , Sudeep Holla , Thomas Gleixner , Will Deacon , linux-arm-kernel@lists.infradead.org, Russell King Subject: [PATCH v7 0/7] Unify CPU topology across ARM & RISC-V Date: Mon, 17 Jun 2019 11:59:13 -0700 Message-Id: <20190617185920.29581-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 and compile tested for ARM64, ARM32 & 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 QEMU changes for RISC-V topology are available at https://github.com/atishp04/qemu/tree/riscv_topology_dt HiFive Unleashed DT with topology node is available here. https://github.com/atishp04/opensbi/tree/HiFive_unleashed_topology It can be verified with OpenSBI with following additional compile time option. FW_PAYLOAD_FDT="unleashed_topology.dtb" 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} | 136 ++++++-- 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, 454 insertions(+), 426 deletions(-) rename Documentation/devicetree/bindings/{arm/topology.txt => cpu/cpu-topology.txt} (66%) -- 2.21.0