Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1719704ybb; Thu, 2 Apr 2020 06:11:42 -0700 (PDT) X-Google-Smtp-Source: APiQypJxy4V2ivumLQo7jcQU4wiMaZbJK0XMEdlhwACjULuJc3lzPEpAXyv2dCVD8cQLSAUa4jyl X-Received: by 2002:a9d:895:: with SMTP id 21mr2179616otf.365.1585833102210; Thu, 02 Apr 2020 06:11:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585833102; cv=none; d=google.com; s=arc-20160816; b=sF74dbicKhAohTs20wif/KCrLEBn7TRmNB9rZO4nKFOac/sreRj2EVUf9ZytbF0RND VGF/OinRtskkhkKCPUbalFAQy16Bdeo3aZ1X/vN0FVstqAgIiXGHoVpF6jeuMYgZP+mb vl+AIx8XCGqoagNrZoiu6QWmtRnHYkhQF7d/LDuOQYONeIpOGUcSI1yC+tGoznnzcIRa FsaSdXGemIRIclWUPOg7lDkvMHIUQtpzEVz+OdqGl/wy0o5ydCF6u6fn2gotll3iI0V5 IzX62stQgnn/Zl04TBCepIlk17I8nmsKT8epgrvq0L+Lscb9vYzIIHpvW6PWkf+U005F iaQQ== 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; bh=L7qOMgMU1P0x+H4plE+KVXZYM+u+mfxREuXsRFFBo3E=; b=lBjRFF0FWfW2wo4kDCxrWHpgHXNNAl+p+efKiaEnI9f3WS8AlIdLUEnLzgJ/MiRuJX dd4ddnCnR6qiaH4WpjnPlB6g1mQm+SllbE0CC58fHhSWIhhFZo+lCCdtPSLWRDDCGR1S GeZpAtV+McSlfzb2+B+4+KeF+kRc09JDO2dmc2pNvZFdGGdEhjZVQvCIRKoViqiiTGLE V++bSEUt5Hz6a6e/CM2P9CJUBJiqdexBPrMdrr56L3l5+HIOb1ms1dkdmumwyRuevc92 O38ReGj7QQgma6T7buwqvQW3CRCqxXBRGYZojFrWnG4AXXqyMfifrgNf30GZMEOg/TSe DO0w== 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 b11si2243765oii.11.2020.04.02.06.11.27; Thu, 02 Apr 2020 06:11:42 -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 S2388361AbgDBNJA (ORCPT + 99 others); Thu, 2 Apr 2020 09:09:00 -0400 Received: from foss.arm.com ([217.140.110.172]:42614 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387580AbgDBNJA (ORCPT ); Thu, 2 Apr 2020 09:09:00 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4B39430E; Thu, 2 Apr 2020 06:08:59 -0700 (PDT) Received: from bogus (unknown [10.37.12.66]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C7AAE3F68F; Thu, 2 Apr 2020 06:08:57 -0700 (PDT) Date: Thu, 2 Apr 2020 14:08:50 +0100 From: Sudeep Holla To: John Garry Cc: rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, jeremy.linton@arm.com, linuxarm@huawei.com, wanghuiqiang@huawei.com, Sudeep Holla Subject: Re: [PATCH] ACPI: PPTT: Inform user that table offset used for Physical processor node ID Message-ID: <20200402123501.GA26588@bogus> References: <1585830145-208714-1-git-send-email-john.garry@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1585830145-208714-1-git-send-email-john.garry@huawei.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (I see 2 copies of this patch, replying on the latest) On Thu, Apr 02, 2020 at 08:22:25PM +0800, John Garry wrote: > If the the Processor ID valid is not set for a Physical Processor Package > node, then the node table offset is used as a substitute. As such, we > may get info like this from sysfs: > > root@(none)$ pwd > /sys/devices/system/cpu/cpu0/topology > root@(none)$ more physical_package_id > 56 > > Inform the user of this in the bootlog, as it is much less than ideal, and > they can remedy this in their FW. > > This topic was originally discussed in: > https://lore.kernel.org/linux-acpi/c325cfe2-7dbf-e341-7f0f-081b6545e890@huawei.com/T/#m0ec18637d8586f832084a8a6af22580e6174669a > Acked-by: Sudeep Holla -- Regards, Sudeep