iommu: Only log strictness for DMA domains

When passthrough is enabled, the default strictness policy becomes
irrelevant, since any subsequent runtime override to a DMA domain type
now embodies an explicit choice of strictness as well. Save on noise by
only logging the default policy when it is meaningfully in effect.

Reviewed-by: John Garry <john.garry@huawei.com>
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Link: https://lore.kernel.org/r/9d2bcba880c6d517d0751ed8bd4960853030b4d7.1628682049.git.robin.murphy@arm.com
Signed-off-by: Joerg Roedel <jroedel@suse.de>

diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
index f653a70..069f7dc 100644 (file)
--- a/drivers/iommu/iommu.c
+++ b/drivers/iommu/iommu.c
@@ -144,10 +144,11 @@ static int __init iommu_subsys_init(void)
                (iommu_cmd_line & IOMMU_CMD_LINE_DMA_API) ?
                        "(set via kernel command line)" : "");
 
-       pr_info("DMA domain TLB invalidation policy: %s mode %s\n",
-               iommu_dma_strict ? "strict" : "lazy",
-               (iommu_cmd_line & IOMMU_CMD_LINE_STRICT) ?
-                       "(set via kernel command line)" : "");
+       if (!iommu_default_passthrough())
+               pr_info("DMA domain TLB invalidation policy: %s mode %s\n",
+                       iommu_dma_strict ? "strict" : "lazy",
+                       (iommu_cmd_line & IOMMU_CMD_LINE_STRICT) ?
+                               "(set via kernel command line)" : "");
 
        return 0;
 }