From: Sudeep Holla <sudeep.holla@arm.com>
To: John Garry <john.garry@huawei.com>
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 <sudeep.holla@arm.com>
Subject: Re: [PATCH] ACPI: PPTT: Inform user that table offset used for Physical processor node ID
Date: Thu, 2 Apr 2020 14:08:50 +0100 [thread overview]
Message-ID: <20200402123501.GA26588@bogus> (raw)
In-Reply-To: <1585830145-208714-1-git-send-email-john.garry@huawei.com>
(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 <sudeep.holla@arm.com>
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-04-02 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 12:22 [PATCH] ACPI: PPTT: Inform user that table offset used for Physical processor node ID John Garry
2020-04-02 13:08 ` Sudeep Holla [this message]
2020-04-02 13:17 ` John Garry
2020-04-02 13:24 ` Hanjun Guo
2020-04-02 13:55 ` Jeremy Linton
2020-04-02 14:51 ` John Garry
2020-04-02 14:54 ` Jeremy Linton
-- strict thread matches above, loose matches on Subject: below --
2020-04-02 10:59 John Garry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200402123501.GA26588@bogus \
--to=sudeep.holla@arm.com \
--cc=jeremy.linton@arm.com \
--cc=john.garry@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=wanghuiqiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.