From: Al Stone <ahs3@redhat.com>
To: Hanjun Guo <guohanjun@huawei.com>, Al Stone <al.stone@linaro.org>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: rjw@rjwysocki.net, lenb@kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, tglx@linutronix.de, jason@lakedaemon.net,
linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org,
linaro-kernel@lists.linaro.org, patches@linaro.org
Subject: Re: [PATCH v3 1/3] ACPI : introduce macros for using the ACPI specification version
Date: Fri, 03 Jul 2015 13:32:33 -0600 [thread overview]
Message-ID: <5596E351.5090100@redhat.com> (raw)
In-Reply-To: <55961AB3.70801@huawei.com>
On 07/02/2015 11:16 PM, Hanjun Guo wrote:
> Hi Al,
>
> On 2015/7/3 7:48, Al Stone wrote:
>> Add the __ACPI_FADT_SPEC_VERSION() helper macro to build a proper version
>> number from a major and minor revision number. Add also macros that use
>> the helper to construct the current version from the values in the FADT
>> (i.e., ACPI_FADT_SPEC_VERSION) and both the 5.1 and 6.0 versions.
>>
>> These macros are added in order to simplify retrieving and comparing ACPI
>> specification version numbers, since this is becoming a more frequent need.
>> In particular, there are some architectures that require at least a certain
>> version of the spec, and there are differences in some structure sizes that
>> have changed with recent versions but can only be tracked by spec version
>> number.
>>
>> Fixes: aeb823bbacc2 (ACPICA: ACPI 6.0: Add changes for FADT table.)
>
> If I understand correctly, will it be (and for next two patches as well):
>
> 0cff8dc0099f (ACPICA: ACPI 6.0: Add changes for MADT table.)?
>
> FADT table update was not introduce any regressions for ARM64
> I think.
>
> Thanks
> Hanjun
>
Right. As I noted in the discussion over v2 of these patches, the FADT
change is correctly implementing a change for ACPI 6.0. However, it is this
change which adds eight bytes to the GICC subtable so that the struct length
and the length field in the GICC subtable no longer match, which is what
causes BAD_MADT_ENTRY to fail.
So, while this commit is correct, the patches in this set are needed to work
around the ambiguity this causes in the spec and the ACPICA implementation of
it.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@redhat.com
-----------------------------------
next prev parent reply other threads:[~2015-07-03 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 23:48 [PATCH v3 0/3] Correct for ACPI 5.1->6.0 spec changes in MADT GICC entries Al Stone
2015-07-02 23:48 ` [PATCH v3 1/3] ACPI : introduce macros for using the ACPI specification version Al Stone
2015-07-03 0:21 ` Rafael J. Wysocki
2015-07-03 5:23 ` Hanjun Guo
2015-07-03 19:22 ` Al Stone
2015-07-03 23:50 ` Rafael J. Wysocki
2015-07-06 21:53 ` Al Stone
2015-07-06 22:44 ` Rafael J. Wysocki
2015-07-03 5:16 ` Hanjun Guo
2015-07-03 19:32 ` Al Stone [this message]
2015-07-02 23:48 ` [PATCH v3 2/3] ACPI / ARM64: add BAD_MADT_GICC_ENTRY() macro Al Stone
2015-07-03 14:06 ` Catalin Marinas
2015-07-03 19:51 ` Al Stone
2015-07-03 23:54 ` Rafael J. Wysocki
2015-07-06 10:33 ` Catalin Marinas
2015-07-06 21:20 ` Al Stone
2015-07-02 23:48 ` [PATCH v3 3/3] ACPI / ARM64 : use the new BAD_MADT_GICC_ENTRY macro Al Stone
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=5596E351.5090100@redhat.com \
--to=ahs3@redhat.com \
--cc=al.stone@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=jason@lakedaemon.net \
--cc=lenb@kernel.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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