Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp2574614imd; Fri, 2 Nov 2018 13:54:56 -0700 (PDT) X-Google-Smtp-Source: AJdET5eLO+qp5gjT6iLurQzJ+v6Z4MZQsvjUZsJSDkTGE4M+rmNVoA8tss+YBAKcWGByGqBxDDI1 X-Received: by 2002:a63:4b60:: with SMTP id k32mr12171879pgl.186.1541192096205; Fri, 02 Nov 2018 13:54:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541192096; cv=none; d=google.com; s=arc-20160816; b=MWtOTOedpmFEuAfBz9plz0/mRUbERVKQdtaABknc2yTlUfpclTRHXBEm6CgxZTGdTH q44L0Q0hFTMCuWvyHE4oYQzX8A2KEDN6LYTDm68sXHbUKtIqXlkm6A/t3bziRSv5MY+D apbu7cD793fqffVqk9M7gbY6iiEIfokev1RkKiu6llk3VPk6TMCQzVifSJ1fizdxLYdo hSj1c7L3+0RfeBmw9kn0H5JOgJEObo0JqFgfpWRRECk68ep7UBPUU3mDcMhDf+F/p3Jp J0Gne+reC2gNOX1mxkt/J36iTIScbnPdBtg1h4/1e/07r6/29JKDbFZlN0/Oopi4CNCn GTXg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=dJB7or3k0ymVkQqcCEeUtRlxqAyp14LoMD6GT+uc5Lw=; b=wI61sXy+tzuKB3BK0offikUFB749fkaIYaZ0/5MHrE2uE0oJXQP+8uZ45523+21sXm ffN2U91KhAkiiovUP3kC2MQa5dwJtqs4iBMpEeOS7V766xLjO4nCo1vmohwKv5KFds/b SuU0YSIFp5V11EHAUXk+17RYN2DUoo1Yi2lLgMjqAvYIVqd4mEyc7k1B2RY3nRLFV2o5 kbjzLwwPIDoJxB67TOWqTIQKIm4exv4xkAxfnHz34D1BJxgp8SfGIiNpqw2sctXgHC5n ncNQIwQoHn5zhR6/LpJ9gEyfP5ICJLtScEyfqs9alyMV5NNalwM9RC2Qg6OU0hz5xjsn T0Jw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@wdc.com header.s=dkim.wdc.com header.b="Ve/93AEt"; 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 185-v6si36346036pff.270.2018.11.02.13.54.41; Fri, 02 Nov 2018 13:54:56 -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="Ve/93AEt"; 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 S1727742AbeKCGCc (ORCPT + 99 others); Sat, 3 Nov 2018 02:02:32 -0400 Received: from esa1.hgst.iphmx.com ([68.232.141.245]:26270 "EHLO esa1.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725957AbeKCGCb (ORCPT ); Sat, 3 Nov 2018 02:02:31 -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=1541192033; x=1572728033; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=h21NZ+6tpNhp03nxgXgjSEzvrceBjFMbjb2yIRYXHWg=; b=Ve/93AEtmm9pBUKTPCU+gXgsGjbh3coV4zZV1YbM5mI24ZmMdJYtw2hy F70+GcVhaof6kkFHwcHpc017EhRsNWsM/KYdUbF1FbdKsa+ZkkfPU/kbT kUSaeLqhvRkoYLCK4Jyv2N1/K++4SLbcRhw//xM0K/5s2iMXIu552jNKb IAznrrOOP/p9LpGO1pQFzsedn4eaQxdMlobVhwgayGbRvJAQffIhEPr3q WtmyrqqzrrBHdc/F2dn/EbBFZljDnRTuj1CCbuoghq+5bB5al4NCT6YTr qyqp17cfN+plaOFLrUObhMypXGFZ1i0HNdh2Ur1mcLcA6gheOhRvq0EZ+ Q==; X-IronPort-AV: E=Sophos;i="5.54,457,1534780800"; d="scan'208";a="197865208" Received: from h199-255-45-14.hgst.com (HELO uls-op-cesaep01.wdc.com) ([199.255.45.14]) by ob1.hgst.iphmx.com with ESMTP; 03 Nov 2018 04:53:52 +0800 Received: from uls-op-cesaip01.wdc.com ([10.248.3.36]) by uls-op-cesaep01.wdc.com with ESMTP; 02 Nov 2018 13:37:46 -0700 Received: from c02v91rdhtd5.sdcorp.global.sandisk.com (HELO [10.111.69.187]) ([10.111.69.187]) by uls-op-cesaip01.wdc.com with ESMTP; 02 Nov 2018 13:53:53 -0700 Subject: Re: [RFC 1/2] dt-bindings: topology: Add RISC-V cpu topology. To: Sudeep Holla , Rob Herring Cc: "linux-riscv@lists.infradead.org" , Palmer Dabbelt , Anup Patel , Christoph Hellwig , Damien Le Moal , Thomas Gleixner , Mark Rutland , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "alankao@andestech.com" , Zong Li References: <1541113468-22097-1-git-send-email-atish.patra@wdc.com> <1541113468-22097-2-git-send-email-atish.patra@wdc.com> <20181102133100.GA13130@e107155-lin> <20181102155038.GA21067@e107155-lin> From: Atish Patra Message-ID: <0c94f752-cc18-ae0c-36e7-7e0dd6b1d307@wdc.com> Date: Fri, 2 Nov 2018 13:53:51 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181102155038.GA21067@e107155-lin> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/2/18 8:50 AM, Sudeep Holla wrote: > On Fri, Nov 02, 2018 at 10:11:38AM -0500, Rob Herring wrote: >> On Fri, Nov 2, 2018 at 8:31 AM Sudeep Holla wrote: >>> >>> On Fri, Nov 02, 2018 at 08:09:39AM -0500, Rob Herring wrote: >>>> On Thu, Nov 1, 2018 at 6:04 PM Atish Patra wrote: >>>>> >>>>> Define a RISC-V cpu topology. This is based on cpu-map in ARM world. >>>>> But it doesn't need a separate thread node for defining SMT systems. >>>>> Multiple cpu phandle properties can be parsed to identify the sibling >>>>> hardware threads. Moreover, we do not have cluster concept in RISC-V. >>>>> So package is a better word choice than cluster for RISC-V. >>>> >>>> There was a proposal to add package info for ARM recently. Not sure >>>> what happened to that, but we don't need 2 different ways. >>>> >>> >>> We still need that, I can brush it up and post what Lorenzo had previously >>> proposed[1]. We want to keep both DT and ACPI CPU topology story aligned. >> >> Frankly, I don't care what the ACPI story is. I care whether each cpu > > Sorry I meant feature parity with ACPI and didn't refer to the mechanics. > >> arch does its own thing in DT or not. If a package prop works for >> RISC-V folks and that happens to align with ACPI, then okay. Though I >> tend to prefer a package represented as a node rather than a property >> as I think that's more consistent. >> > > Sounds good. One of the reason for making it *optional* property is for > backward compatibility. But we should be able to deal with that even with > node. > If you are introducing a package node, can we make cluster node optional? I feel it is a redundant node for use cases where one doesn't have a different grouped cpus in a package. We may have some architecture that requires cluster, it can be added to the DT at that time, I believe. >> Any comments on the thread aspect (whether it has ever been used)? >> Though I think thread as a node level is more consistent with each >> topology level being a node (same with package). >> > Not 100% sure, the only multi threaded core in the market I know is > Cavium TX2 which is ACPI. > Any advantages of keeping thread node if it's not being used. If I am not wrong, we can always use multiple cpuN phandles to represent SMT nodes. It will result in less code and DT documentation as well. Regards, Atish > -- > Regards, > Sudeep >