From: Sudeep Holla <sudeep.holla@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Jeremy Linton <jeremy.linton@arm.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"liuqi (BA)" <liuqi115@huawei.com>,
wanghuiqiang <wanghuiqiang@huawei.com>,
"wangxiongfeng (C)" <wangxiongfeng2@huawei.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: About PPTT find_acpi_cpu_topology_package()
Date: Thu, 13 Feb 2020 14:00:06 +0000 [thread overview]
Message-ID: <20200213140006.GB31787@bogus> (raw)
In-Reply-To: <b9ca7718-3834-b42d-a36e-63c81f677a78@huawei.com>
On Thu, Feb 13, 2020 at 11:52:09AM +0000, John Garry wrote:
[...]
>
> As for when it's not set, it's unclear. My understanding is that the ACPI
> processor id should still be used as the non-leaf node identifier, but it
> would not match a UID for a processor container (as it may not exist).
>
I can't infer anything that matches your understanding from the spec in
this regard. If it's not set, then it is left to OSPM.
> The kernel does have behave according to this.
>
According to what in the specification ?
> So how I am misinterpreting this?
>
May be you are not, it is just ambiguous in the spec, worth checking and
fixing if it is an issue. I reiterate we don't want to generate anything
in the OS for this purpose.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-02-13 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 11:20 About PPTT find_acpi_cpu_topology_package() John Garry
2020-02-12 11:59 ` Sudeep Holla
2020-02-12 12:48 ` John Garry
2020-02-12 13:55 ` Sudeep Holla
2020-02-11 18:49 ` Jeremy Linton
2020-02-12 15:36 ` Sudeep Holla
2020-02-12 14:41 ` John Garry
2020-02-11 19:01 ` Jeremy Linton
2020-03-25 11:43 ` John Garry
2020-02-11 19:31 ` Jeremy Linton
2020-02-12 16:41 ` John Garry
2020-02-11 21:12 ` Jeremy Linton
2020-02-13 11:52 ` John Garry
2020-02-13 14:00 ` Sudeep Holla [this message]
2020-02-13 14:33 ` John Garry
2020-02-13 16:52 ` Jeremy Linton
2020-02-14 10:35 ` John Garry
2020-02-14 11:22 ` Sudeep Holla
2020-02-12 15:32 ` Sudeep Holla
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=20200213140006.GB31787@bogus \
--to=sudeep.holla@arm.com \
--cc=guohanjun@huawei.com \
--cc=jeremy.linton@arm.com \
--cc=john.garry@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=liuqi115@huawei.com \
--cc=wanghuiqiang@huawei.com \
--cc=wangxiongfeng2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).