Skip to content

Commit d8577d2

Browse files
John Garryjoergroedel
authored andcommitted
iommu: Print strict or lazy mode at init time
As well as the default domain type, it's useful to know whether strict or lazy for DMA domains, so add this info in a separate print. The (stict/lazy) mode may be also set via iommu.strict earlyparm, but this will be processed prior to iommu_subsys_init(), so that print will be accurate for drivers which don't set the mode via custom means. For the drivers which set the mode via custom means - AMD and Intel drivers - they maintain prints to inform a change in policy or that custom cmdline methods to change policy are deprecated. Signed-off-by: John Garry <[email protected]> Reviewed-by: Robin Murphy <[email protected]> Reviewed-by: Lu Baolu <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Joerg Roedel <[email protected]>
1 parent 1d479f1 commit d8577d2

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

drivers/iommu/iommu.c

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,11 @@ static int __init iommu_subsys_init(void)
139139
(iommu_cmd_line & IOMMU_CMD_LINE_DMA_API) ?
140140
"(set via kernel command line)" : "");
141141

142+
pr_info("DMA domain TLB invalidation policy: %s mode %s\n",
143+
iommu_dma_strict ? "strict" : "lazy",
144+
(iommu_cmd_line & IOMMU_CMD_LINE_STRICT) ?
145+
"(set via kernel command line)" : "");
146+
142147
return 0;
143148
}
144149
subsys_initcall(iommu_subsys_init);

0 commit comments

Comments
 (0)