From: Sudeep Holla <sudeep.holla@arm.com>
To: Shunyong Yang <shunyong.yang@hxt-semitech.com>, catalin.marinas@arm.com
Cc: Sudeep Holla <sudeep.holla@arm.com>,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
jeremy.linton@arm.com, Joey Zheng <yu.zheng@hxt-semitech.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [RFC PATCH] arm64: topology: Map PPTT node offset to logic physical package id
Date: Thu, 28 Jun 2018 10:38:24 +0100 [thread overview]
Message-ID: <cb057c6a-0eb4-581e-c259-7a31545e0ae7@arm.com> (raw)
In-Reply-To: <1530177508-15298-1-git-send-email-shunyong.yang@hxt-semitech.com>
Hi Shunyong,
On 28/06/18 10:18, Shunyong Yang wrote:
> As PPTT spec doesn't define the physical package id,
> find_acpi_cpu_topology_package() will return offset of the node with
> Physical package field set when querying physical package id. So, it
> returns 162(0xA2) in following example.
>
> [0A2h 0162 1] Subtable Type : 00 [Processor Hierarchy
> Node]
> [0A3h 0163 1] Length : 1C
> [0A4h 0164 2] Reserved : 0000
> [0A6h 0166 4] Flags (decoded below) : 00000003
> Physical package : 1
> ACPI Processor ID valid : 1
> [0AAh 0170 4] Parent : 00000000
> [0AEh 0174 4] ACPI Processor ID : 00001000
> [0B2h 0178 4] Private Resource Number : 00000002
> [0B6h 0182 4] Private Resource : 0000006C
> [0BAh 0186 4] Private Resource : 00000084
>
> So, when "cat physical_package" in /sys/devices/system/cpu/cpu0/topology/,
> it will output 162(0xA2). And if some items are added before the node
> above, the output will change to other value.
>
> This patch maps the node offset to a logic package id. It maps the first
> node offset to 0, the second to 1, and so on.
>
> Then, it will not output a big value, such as 162 above. And it will
> not change when some nodes(Physical package not set) are added.
>
> And as long as the nodes with Physical package field set in PPTT keeps
> the real hardware order, the logic id can map to hardware package id to
> some extent.
>
> Hope to get feedback from you.
Thanks for the patch, but Andrew Jones has also posted a patch[1] which
I had a look but was not sure what is the best approach to fix it yet.
I will think about it and respond to that.
--
Regards,
Sudeep
[1] https://patchwork.kernel.org/patch/10482261
next prev parent reply other threads:[~2018-06-28 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 9:18 Shunyong Yang
2018-06-28 9:38 ` Sudeep Holla [this message]
2018-06-28 11:57 ` Andrew Jones
2018-06-28 12:12 ` Sudeep Holla
2018-06-28 13:19 ` Jeremy Linton
2018-06-28 14:09 ` Sudeep Holla
2018-06-28 14:51 ` Andrew Jones
2018-06-28 15:44 ` Yang, Shunyong
2018-06-28 16:45 ` Sudeep Holla
2018-07-12 11:06 ` Will Deacon
2018-07-12 11:20 ` 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=cb057c6a-0eb4-581e-c259-7a31545e0ae7@arm.com \
--to=sudeep.holla@arm.com \
--cc=catalin.marinas@arm.com \
--cc=drjones@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shunyong.yang@hxt-semitech.com \
--cc=will.deacon@arm.com \
--cc=yu.zheng@hxt-semitech.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
all inboxes | Powered by JetHome®