Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp1134758ybi; Fri, 12 Jul 2019 10:17:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqy8J0QuqxvNIJugaGMG/0g5k8NQJZ/FdTysNOaRIDB+NQEU0T1vvlUbtCK5vpSxzE5OuJpA X-Received: by 2002:a17:902:4283:: with SMTP id h3mr12401476pld.15.1562951869855; Fri, 12 Jul 2019 10:17:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562951869; cv=none; d=google.com; s=arc-20160816; b=YxnRIF4FSwUMXmJRxnlw04VZQ8xQB9F/r8wWzmchGDv83xKQz6VUKrgTJHdFRlzmtO lEXoKjYhI/jYq7+oWy1V6YERR7Pdhsl3WCzIEnp+bv0RR4OwhdUn0hT4zIUagXwJKs65 yCskvkSD/BSeTCjD4NTtvim8tINNXfwQH46+8ciSrSFXDoaTSfU92Ga+jrblDOP/wdA3 /jXnApgp9mKW05KsNmhYyIh2t+d60blAL4DVOGgjIbBxJ8Zbsta6PD7qMGURGOl1rkpC bxsmwSzRNd6UMvQ28JOCF96/97d6nIXj7vlvlOux1L9ePnKlAVe1nHAXEd+mpkaj84Qv QatA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date:dkim-signature; bh=iXtdpQd8nnhs4LGXKgAYAQvupi8/WOX4e9Rzt2Cr9CU=; b=Kj1TQzCm+uuvfV9Z0JBLVtKuYDXZhO2H/BmEY99Le8c7DrByu0TlobEVE32xIu0xw0 raEnLYNs4uenObd3h1walfRZzMn4Xh4UUnLsKqVsCMyR6sMPiQo96ncPOhabsbMoOYiH EL7yqHlOSuzTqzlanhl4PAqxtAhtqa/SblrZw2iIReCoNo26SMZc72GXkc+3TdDvOUf2 J6ozKImFLxE0RRsbqcYT0gJWU2cALu6cargf40ChxFBra3ar7C+HhDdvgBzYWrzPHBsU LFUDi7nFI9K5NT4xkWDdKS/Ad4vTkcHlmpjz+2rhItkQ4ZqLuDfKa6Qh/Ri0w7t0Wph6 ItgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b="YT2j/iU4"; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m63si8860594pjb.8.2019.07.12.10.17.32; Fri, 12 Jul 2019 10:17:49 -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=pass header.i=@sifive.com header.s=google header.b="YT2j/iU4"; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727024AbfGLRQn (ORCPT + 99 others); Fri, 12 Jul 2019 13:16:43 -0400 Received: from mail-io1-f68.google.com ([209.85.166.68]:41136 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726907AbfGLRQm (ORCPT ); Fri, 12 Jul 2019 13:16:42 -0400 Received: by mail-io1-f68.google.com with SMTP id j5so17715010ioj.8 for ; Fri, 12 Jul 2019 10:16:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=iXtdpQd8nnhs4LGXKgAYAQvupi8/WOX4e9Rzt2Cr9CU=; b=YT2j/iU40MxuBBXO9lb5IQbBE5jrkfnrRY9xLOdGAaikbSdl2YU6uISPilY0ddfipw SPtU62qkG3Z5Z3Ogc2azK7ti8QpOISRgUsmIIABxcIsT1X+rWxrTo6IzUEhlO1bsVrAX IveXj25vZsg7hNSxNfVrqRhQ0scEmYofrPVcosq7oaf1o1lzV41Pxc/GvnY5xxtmwY2K fevC+u/BdbIWXOzlfkUy2QZuiBwhUm4UUuihyenGCKdHe92z/Ub/e3biIlISfJPE1eXI plfC/5M62ssyRlos7GBsgbXMMsn21QEaFARhtqdvHLFp5TTp0Ko2bKH5YUaAl4pEeEEd ub5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=iXtdpQd8nnhs4LGXKgAYAQvupi8/WOX4e9Rzt2Cr9CU=; b=bEQpzorFw8Zua6YPalVb1bWOpJc60XvwyteGw/hsEWWunjG4zAQHCT8F/sr3v78o9c nIV40zqjU8ftKVqb+orRNnhRy/kaNbCZaIf2XFj5qoDkFcnsPPfO35NbHi9UPsTPyu5T zj7YdWQLTe07EmfnoPGuat8g4ZsElqtI8ZBh6VljBmC9WlEFaW5s231rhwBpwJKkYHFL gHxrrccnC3mBQ5h0O1Ysu2kRbe0d8XaIDQ4zTCQSqoRdEu2xYSZP9wcWt9oiZDl+Vwrs zO1cyACAYnHH9PaUz8cSEP1WI7ZTQbIWU8JfjWJ7Biqbjy3zBgdGqw/nnoSICUE30FEJ BLbw== X-Gm-Message-State: APjAAAXzdStbcrWXxogKqcZ7xCd2nWbpfRk70afxS5iaXiI5F6FRlBSm uiPYzyqKQB3Rx03jFjmoKDPXnw== X-Received: by 2002:a6b:7d49:: with SMTP id d9mr12058493ioq.50.1562951801913; Fri, 12 Jul 2019 10:16:41 -0700 (PDT) Received: from localhost (67-0-62-24.albq.qwest.net. [67.0.62.24]) by smtp.gmail.com with ESMTPSA id c81sm13381678iof.28.2019.07.12.10.16.41 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 12 Jul 2019 10:16:41 -0700 (PDT) Date: Fri, 12 Jul 2019 10:16:40 -0700 (PDT) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Atish Patra cc: linux-kernel@vger.kernel.org, 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 , "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: Re: [PATCH v8 0/7] Unify CPU topology across ARM & RISC-V In-Reply-To: <20190627195302.28300-1-atish.patra@wdc.com> Message-ID: References: <20190627195302.28300-1-atish.patra@wdc.com> User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Folks, On Thu, 27 Jun 2019, Atish Patra wrote: > 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. Since these patches touch files across several different architectures, and thus really should sit in -next for a while; and because it's late in the merge window, I'm planning to postpone sending these patches upstream until after v5.3-rc1 is released. Once v5.3-rc1 is released, let's plan to get these patches rebased and reposted and into linux-next as soon as possible. Sorry for the delay here, - Paul