On Thu, 29 Jan 2026 at 13:36, Peter Maydell <[email protected]> wrote: > > On Tue, 27 Jan 2026 at 18:28, Mohamed Mediouni <[email protected]> > wrote: > > > > After the previous commit introducing GICv3 + GICv2m configurations, > > update the AArch64 ACPI tables for the GICv2 case. > > > > Signed-off-by: Mohamed Mediouni <[email protected]> > > --- > > tests/data/acpi/aarch64/virt/IORT | Bin 128 -> 84 bytes > > tests/data/acpi/aarch64/virt/IORT.smmuv3-dev | Bin 364 -> 260 bytes > > tests/data/acpi/aarch64/virt/IORT.smmuv3-legacy | Bin 276 -> 192 bytes > > tests/qtest/bios-tables-test-allowed-diff.h | 3 --- > > 4 files changed, 3 deletions(-) > > The process documented in tests/qtest/bios-tables-test.c says > that this commit is supposed to have the diff of the disassembled > table data in the commit message, so that human reviewers can > confirm that the changes are as expected. (If you git log > tests/data/acpi you can see how this looks.) > > Can you provide the ASL diff, please? (If this is going to be the > only fix needed to this version of the series, which I hope it > will be, then I can update the commit message as I apply the > series, so you don't need to respin, just reply with the updated > commit message with the diff in it.)
...ah, it looks like unfortunately this is going to conflict with the smmuv3 acceleration series I already have queued, because that series also updates these ACPI blobs. So I think the best thing is if I get that out in a target-arm pullreq and then you can rebase on top of that. thanks -- PMM
