From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Jeremy Linton <jeremy.linton@arm.com>,
shunyong.yang@hxt-semitech.com, yu.zheng@hxt-semitech.com,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Andrew Jones <drjones@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] ACPI/PPTT: use ACPI ID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set
Date: Mon, 2 Jul 2018 13:52:24 +0100 [thread overview]
Message-ID: <8fe4ee5c-23b8-12bb-3f2e-5589ca4de24b@arm.com> (raw)
In-Reply-To: <CAJZ5v0gh0-psU7bbLf5zDGW5adQNALSdWdedbCgDoh1F-peh0g@mail.gmail.com>
On 02/07/18 12:01, Rafael J. Wysocki wrote:
> On Mon, Jul 2, 2018 at 11:57 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>
>>
>> On 02/07/18 10:06, Rafael J. Wysocki wrote:
>>> On Fri, Jun 29, 2018 at 6:17 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>>> Currently we use the ACPI processor ID only for the leaf/processor nodes
>>>> as the specification states it must match the value of ACPI processor ID
>>>> field in the processor’s entry in the MADT.
>>>>
>>>> However, if a PPTT structure represents processors group, it match a
>>>> processor container UID in the namespace and ACPI_PPTT_ACPI_PROCESSOR_ID_VALID
>>>> flag describe whether the ACPI processor ID is valid.
>>>>
>>>> Lets use UID whenever ACPI_PPTT_ACPI_PROCESSOR_ID_VALID is set to be
>>>> consistent instead of using table offset as it's currently done for non
>>>> leaf nodes.
>>>>
>>>> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
>>>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>>>> ---
>>>> drivers/acpi/pptt.c | 10 ++++++++--
>>>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>>>
>>>> Hi,
>>>>
>>>> There's ongoing discussion on assigning ID based in OS using simple
>>>> counters. It can never be consistent with firmware's view. So if the
>>>> firmware provides valid UID for non-processors node, we must use it.
>>>
>>> OK
>>>
>>> Do you regard this as a fix for the recently merged PPTT material? If
>>> so, I should apply it as a fix for 4.18.
>>>
>>
>> Yes, it should be considered as fix IMO.
>
> So any chance to provide a Fixes: tag?
Sure, since it was in the same release, I didn't add it.
Fixes: 2bd00bcd73e5 ("ACPI/PPTT: Add Processor Properties Topology Table
parsing")
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-07-02 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 16:17 Sudeep Holla
2018-06-29 18:18 ` Jeremy Linton
2018-07-02 10:08 ` Sudeep Holla
2018-06-30 7:16 ` Andrew Jones
2018-07-02 10:01 ` Sudeep Holla
2018-07-02 9:06 ` Rafael J. Wysocki
2018-07-02 9:57 ` Sudeep Holla
2018-07-02 11:01 ` Rafael J. Wysocki
2018-07-02 12:52 ` Sudeep Holla [this message]
2018-07-04 10:38 ` Rafael J. Wysocki
2018-07-02 14:41 ` Jeremy Linton
2018-07-02 13:23 ` Jeremy Linton
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=8fe4ee5c-23b8-12bb-3f2e-5589ca4de24b@arm.com \
--to=sudeep.holla@arm.com \
--cc=catalin.marinas@arm.com \
--cc=drjones@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--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
Powered by JetHome