From: al.stone@linaro.org (Al Stone)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ACPI: add BAD_MADT_GICC_ENTRY() macro
Date: Thu, 18 Jun 2015 16:36:07 -0600 [thread overview]
Message-ID: <1434666968-1543-3-git-send-email-al.stone@linaro.org> (raw)
In-Reply-To: <1434666968-1543-1-git-send-email-al.stone@linaro.org>
The BAD_MADT_ENTRY() macro is designed to work for all of the subtables
of the MADT. In the ACPI 5.1 version of the spec, the struct for the
GICC subtable (struct acpi_madt_generic_interrupt) is 76 bytes long; in
ACPI 6.0, the struct is 80 bytes long. But, there is only one definition
in ACPICA for this struct -- and that is the 6.0 version. Hence, when
BAD_MADT_ENTRY() compares the struct size to the length in the GICC
subtable, it fails if 5.1 structs are in use, and there are systems in
the wild that have them.
This patch adds the BAD_MADT_GICC_ENTRY() that checks the GICC subtable
only, accounting for the difference in specification versions that are
possible. The BAD_MADT_ENTRY() will continue to work as is for all other
MADT subtables.
Signed-off-by: Al Stone <al.stone@linaro.org>
---
include/linux/acpi.h | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/include/linux/acpi.h b/include/linux/acpi.h
index 33ed313..d3a1758 100644
--- a/include/linux/acpi.h
+++ b/include/linux/acpi.h
@@ -127,6 +127,16 @@ static inline void acpi_initrd_override(void *data, size_t size)
(!entry) || (unsigned long)entry + sizeof(*entry) > end || \
((struct acpi_subtable_header *)entry)->length < sizeof(*entry))
+#define ACPI_MADT_GICC_51_LENGTH 76
+#define ACPI_MADT_GICC_60_LENGTH 80
+
+#define BAD_MADT_GICC_ENTRY(entry, end) ( \
+ (!entry) || (unsigned long)entry + sizeof(*entry) > end || \
+ ((ACPI_FADT_SPEC_VERSION == ACPI_SPEC_VERSION(5, 1)) && \
+ (entry->header.length != ACPI_MADT_GICC_51_LENGTH)) || \
+ ((ACPI_FADT_SPEC_VERSION == ACPI_SPEC_VERSION(6, 0)) && \
+ (entry->header.length != ACPI_MADT_GICC_60_LENGTH)))
+
char * __acpi_map_table (unsigned long phys_addr, unsigned long size);
void __acpi_unmap_table(char *map, unsigned long size);
int early_acpi_boot_init(void);
--
2.4.0
next prev parent reply other threads:[~2015-06-18 22:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 22:36 [PATCH v2 0/3] Correct for ACPI 5.1->6.0 spec changes in MADT GICC entries Al Stone
2015-06-18 22:36 ` [PATCH v2 1/3] ACPI : introduce macros for using the ACPI specification version Al Stone
2015-06-19 10:49 ` Hanjun Guo
2015-06-19 20:01 ` Al Stone
2015-06-30 20:12 ` Rafael J. Wysocki
2015-06-30 21:15 ` Al Stone
2015-07-01 2:30 ` Hanjun Guo
2015-06-18 22:36 ` Al Stone [this message]
2015-06-19 10:49 ` [PATCH v2 2/3] ACPI: add BAD_MADT_GICC_ENTRY() macro Hanjun Guo
2015-06-19 20:02 ` Al Stone
2015-06-18 22:36 ` [PATCH v2 3/3] ACPI / ARM64 : use the new BAD_MADT_GICC_ENTRY macro Al Stone
2015-06-19 9:46 ` Will Deacon
2015-06-19 20:03 ` Al Stone
2015-06-19 10:52 ` Hanjun Guo
2015-06-19 10:54 ` [PATCH v2 0/3] Correct for ACPI 5.1->6.0 spec changes in MADT GICC entries Hanjun Guo
2015-06-19 20:05 ` Al Stone
2015-06-30 17:07 ` Sudeep Holla
2015-06-30 17:29 ` Al Stone
2015-06-30 18:25 ` Rafael J. Wysocki
2015-06-30 18:35 ` Rafael J. Wysocki
2015-07-01 2:06 ` Hanjun Guo
2015-07-02 18:25 ` Al Stone
2015-06-30 18:39 ` Al Stone
2015-06-30 19:05 ` Rafael J. Wysocki
2015-06-30 19:57 ` Al Stone
2015-06-30 19:45 ` Al Stone
2015-06-30 19:58 ` Rafael J. Wysocki
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=1434666968-1543-3-git-send-email-al.stone@linaro.org \
--to=al.stone@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).