Enable CONFIG_ARM_SMMU and CONFIG_ARM_SMMU_V3 in aarch64.

[ddaney-fungible]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Enable IOMMU in aarch64 kernel. It is needed to allow VFIO to be used with Mariner.

Change Log

• Enable CONFIG_ARM_SMMU and CONFIG_ARM_SMMU_V3 in aarch64 kernel.

Does this affect the toolchain?

NO

Associated issues

• Add CONFIG_ARM_SMMU{,_V3} to aarch64 kernel config #6818

Test Methodology

• local build

[charles-gray]

Nice!!

[christopherco]

Hi @ddaney-fungible thanks for the contribution! I will request to retarget your PR to our main branch instead of the 2.0 branch.
main is our 2.0 development branch so changes will flow there first.

[christopherco]

Added a couple other comments, but aside from retargeting to main, the changes seem reasonable to me. Once retargeted, @rlmenge let's kick off our official buddy builds to test fully out this change

Note: We'll also want to make sure this change gets cherry-picked into our 3.0-dev branch as well, so it is part of our next major 3.0 release. But let's first get this PR evaluated/merged into our main branch

[christopherco]

Please add a corresponding changelog entry in the %changelog section for this -2 release increment

[christopherco]

Please add a corresponding changelog entry in the %changelog section for this -2 release increment

[christopherco]

Please add a corresponding changelog entry in the %changelog section for this -2 release increment

[ddaney-fungible]

Thanks for the feedback, I don't know how to change the branch target of a PR, so I am going to close this one and open a new one for the main branch.