[PATCH v2] iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases

[Jason Gunthorpe]

On Mon, 03 Nov 2025 09:27:55 -0800, Nicolin Chen wrote:
> A vDEVICE has been a hard requirement for attaching a nested domain to the
> device. This makes sense when installing a guest STE, since a vSID must be
> present and given to the kernel during the vDEVICE allocation.
> 
> But, when CR0.SMMUEN is disabled, VM doesn't really need a vSID to program
> the vSMMU behavior as GBPA will take effect, in which case the vSTE in the
> nested domain could have carried the bypass or abort configuration in GBPA
> register. Thus, having such a hard requirement doesn't work well for GBPA.
> 
> [...]

Applied, thanks!

[1/1] iommu/arm-smmu-v3-iommufd: Allow attaching nested domain for GBPA cases
      https://git.kernel.org/jgg/iommufd/c/9f0b286fe40130

Best regards,
-- 
Jason Gunthorpe <jgg at nvidia.com>