[+Catalin, Will, Shameer]Yes, that is a valid fix. Unlikely it will be a problem. Anyway, I have requested
On Mon, Jul 17, 2023 at 07:33:45PM +0800, Guanghui Feng wrote:
According to the ARM IORT specifications DEN 0049 issue E,reserved regions")
the "Number of IDs" field in the ID mapping format reports
the number of IDs in the mapping range minus one.
In iort_node_get_rmr_info(), we erroneously skip ID mappings
whose "Number of IDs" equal to 0, resulting in valid mapping
nodes with a single ID to map being skipped, which is wrong.
Fix iort_node_get_rmr_info() by removing the bogus id_count
check.
Fixes: 491cf4a6735a ("ACPI/IORT: Add support to retrieve IORT RMR
Signed-off-by: Guanghui Feng<guanghuifeng@xxxxxxxxxxxxxxxxx>acpi_iort_node *node,
---
drivers/acpi/arm64/iort.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c
index 3631230..56d8873 100644
--- a/drivers/acpi/arm64/iort.c
+++ b/drivers/acpi/arm64/iort.c
@@ -1007,9 +1007,6 @@ static void iort_node_get_rmr_info(struct
for (i = 0; i < node->mapping_count; i++, map++) {Shameer, I know this may look like overkill since the hunk we are
struct acpi_iort_node *parent;
- if (!map->id_count)
- continue;
-
parent = ACPI_ADD_PTR(struct acpi_iort_node, iort_table,
map->output_reference);
if (parent != iommu)
removing is buggy but can you please test this patch on platforms
with RMR to make sure we are not triggering regressions by removing
it (by the specs that's what should be done but current firmware
is always something to reckon with) ?
Hanjun to help with the testing as I don't have a test setup with me now.
Hanjun, please help.