Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp622479imm; Fri, 29 Jun 2018 03:45:10 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIK2LY5ayMaY/qPB7LAT2UhP6MGFzY6fkJWCimKxj5MFSrIa6QdrK9/2955hbZwW2Lqqbn8 X-Received: by 2002:a17:902:8607:: with SMTP id f7-v6mr14474069plo.138.1530269110848; Fri, 29 Jun 2018 03:45:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530269110; cv=none; d=google.com; s=arc-20160816; b=vN7TCxkbcWRtzgWw7vK8W6flXXd3wokLyg56Da0cwwFobP1Xmy6p/nnQG54eCPLk2O cMmIvJv4LVu9kGOuj5qV2uD1iauVYD80d/J8SjDfQB5ja0yis6HZC5omfM4BOk454STz lcs7cVzvxc59mZzKrqSgG0dB7Z3IRiD26ZuD6HAZ+vfcsRP1BnFvPyQo4xzyAbAHlwcE q8I0Y7mraX3cFG8VloNi9R3kpTWrfn+g8XcxAIl0CQwFtjm4cZ6WPaqerfBG1hhrJl6R 1a4/gw66fxBaVllCbfC6wa2A6YKBUMfdifvQnJzX3ghiWqxE2PbaInwNzwWdluKknxD5 /t3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=z2V+woqRhoah2YrEh5rABYxfy7hfExgFg3+Y2w7T/7Q=; b=JcJ1hFlrwtwTCZa8/4SmlhoBGfEU8FwRPfNKEyg8iztYqFUv8XIMIsxwERyv9iaPEf E1+k361lle8BW9T5diNrq0lxbRmdsa9igIGhCpeI9R0uoRwaRU4022u+jRUYb0vJO076 muyq273aTPbinNrC74fA4GolUVFh7N4+VViFZVESjrdy6NQAi5gJ17ZBLTqI+qX+3K4M +URF4iKrdmDUwildpLvuH96OjYiB28N6bbZMfBDK3i+hpNI/ejM/wVLo4f99b4/coj9t ovpkSYoVHF6/3/Iv78QJcVPA4XQjNFXnp1l8XF+XVCwCLEvWh1iOamJdG8CFOZGHGKSL W3Dw== ARC-Authentication-Results: i=1; mx.google.com; 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 f90-v6si9388821plf.390.2018.06.29.03.44.56; Fri, 29 Jun 2018 03:45:10 -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; 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 S1754864AbeF2K3l (ORCPT + 99 others); Fri, 29 Jun 2018 06:29:41 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:59332 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754814AbeF2K3k (ORCPT ); Fri, 29 Jun 2018 06:29:40 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id CFDCB18A; Fri, 29 Jun 2018 03:29:39 -0700 (PDT) Received: from e107155-lin (unknown [10.1.210.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 34C123F266; Fri, 29 Jun 2018 03:29:38 -0700 (PDT) Date: Fri, 29 Jun 2018 11:29:27 +0100 From: Sudeep Holla To: Andrew Jones Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, jeremy.linton@arm.com, ard.biesheuvel@linaro.org, shunyong.yang@hxt-semitech.com, yu.zheng@hxt-semitech.com, catalin.marinas@arm.com, will.deacon@arm.com Subject: Re: [PATCH] arm64: acpi: reenumerate topology ids Message-ID: <20180629102927.GA18043@e107155-lin> References: <20180628145128.10057-1-drjones@redhat.com> <20180628173243.obydzakh2stfs26w@kamzik.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180628173243.obydzakh2stfs26w@kamzik.brq.redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 28, 2018 at 07:32:43PM +0200, Andrew Jones wrote: > On Thu, Jun 28, 2018 at 05:30:51PM +0100, Sudeep Holla wrote: > > I am not sure if we can ever guarantee that DT and ACPI will get the > > same ids whatever counter we use as it depends on the order presented in > > the firmware(DT or ACPI). So I am not for generating ids for core and > > threads in that way. > > I don't believe we have to guarantee that the exact (package,core,thread) > triplet describing a PE with DT matches ACPI. We just need to guarantee > that each triplet we select properly puts a PE in the same group as its > peers. So, as long as we keep the grouping described by DT or ACPI, then > the (package,core,thread) IDs assigned are pretty arbitrary. > If that's the requirement, we already do that. The IDs are just too arbitrary :) > I could change the commit message to state we can generate IDs *like* > DT does (i.e. with counters), even if they may not result in identical > triplet to PE mappings. > Why we need to make it *like DT* ? > > > > So I would like to keep it simple and just have this counters for > > package ids as demonstrated in Shunyong's patch. > > > > If we don't also handle cores when there are threads, then the cores > will also end up having weird IDs. > Yes, but if PPTT says it has valid ID, I would prefer that over DT like generated. -- Regards, Sudeep