| commit | b645f0fcb4e80cb5fa914bae6e7a1aff352b5b47 | |
| author | Andrea Bolognani <abologna@redhat.com> | |
| Tue, 28 May 2019 14:00:57 +0000 (28 16:00 +0200) | ||
| committer | Andrea Bolognani <abologna@redhat.com> | |
| Mon, 3 Jun 2019 15:40:54 +0000 (3 17:40 +0200) | ||
| tree | 61be6a05a129256d10ed452422187fa706eff064 | treesnapshot (tar.gz zip) |
| parent | fc660ae3154de21ec3214be2551befff3d508cb5 | commitdiff |
qemu: Move capability checks for IOMMU features
All current IOMMU features are specific to Intel IOMMU, so
understandably we check for the corresponding capabilities
inside the Intel-specific switch() branch; however, we want
to make sure SMMUv3 IOMMU users get an error if they try to
enable any of those features in their guest, and performing
the capability checks unconditionally is both the easiest
way to achieve that, as well as the one least likely to
result in us inadvertently letting users enable some new
Intel-specific IOMMU feature for ARM guests later on.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
All current IOMMU features are specific to Intel IOMMU, so
understandably we check for the corresponding capabilities
inside the Intel-specific switch() branch; however, we want
to make sure SMMUv3 IOMMU users get an error if they try to
enable any of those features in their guest, and performing
the capability checks unconditionally is both the easiest
way to achieve that, as well as the one least likely to
result in us inadvertently letting users enable some new
Intel-specific IOMMU feature for ARM guests later on.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
| src/qemu/qemu_domain.c | diffblobblamehistory |