[PATCH v3 0/2] Respect VASIZE for address limits

[Ankit Soni <Ankit.Soni@amd.com>]

The AMD IOMMU driver was only using EFR[HATS] to derive the VA size,
ignoring the IVINFO[VASIZE] limit. This could create domains that
exceed the bounds advertised by hypervisor.

Patch 1 removes PT_FEAT_DYNAMIC_TOP from PT_FORCE_ENABLED_FEATURES
to fix a spurious domain allocation failure when the VA size is small
enough that dynamic top growth is unnecessary.

Patch 2 makes the driver respect IVINFO[VASIZE] when determining the
addressable VA range.

Changes:
v3: - Remove specific value checking for vasize.
    - Add patch for PT_FORCE_ENABLED_FEATURES.

v2: - Mark ivinfo_vasize_bits() as __init.

Ankit Soni (2):
  iommu/amd: Remove PT_FEAT_DYNAMIC_TOP from PT_FORCE_ENABLED_FEATURES
  iommu/amd: Adhere to IVINFO[VASIZE] for address limits

 drivers/iommu/amd/amd_iommu.h              |  2 +-
 drivers/iommu/amd/amd_iommu_types.h        |  1 +
 drivers/iommu/amd/init.c                   | 13 +++++++++----
 drivers/iommu/amd/iommu.c                  |  3 +--
 drivers/iommu/generic_pt/fmt/iommu_amdv1.c |  2 +-
 5 files changed, 13 insertions(+), 8 deletions(-)

-- 
2.43.0