Skip to content

Commit 804f98e

Browse files
LuBaoluwilldeacon
authored andcommitted
iommu/vt-d: Downgrade warning for pre-enabled IR
Emitting a warning is overkill in intel_setup_irq_remapping() since the interrupt remapping is pre-enabled. For example, there's no guarantee that kexec will explicitly disable interrupt remapping before booting a new kernel. As a result, users are seeing warning messages like below when they kexec boot a kernel, though there is nothing wrong: DMAR-IR: IRQ remapping was enabled on dmar18 but we are not in kdump mode DMAR-IR: IRQ remapping was enabled on dmar17 but we are not in kdump mode DMAR-IR: IRQ remapping was enabled on dmar16 but we are not in kdump mode ... ... Downgrade the severity of this message to avoid user confusion. CC: Paul Menzel <[email protected]> Link: https://lore.kernel.org/linux-iommu/[email protected]/ Signed-off-by: Lu Baolu <[email protected]> Reviewed-by: Kevin Tian <[email protected]> Link: https://lore.kernel.org/r/[email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Will Deacon <[email protected]>
1 parent e995fcd commit 804f98e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

drivers/iommu/intel/irq_remapping.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -597,8 +597,8 @@ static int intel_setup_irq_remapping(struct intel_iommu *iommu)
597597

598598
if (ir_pre_enabled(iommu)) {
599599
if (!is_kdump_kernel()) {
600-
pr_warn("IRQ remapping was enabled on %s but we are not in kdump mode\n",
601-
iommu->name);
600+
pr_info_once("IRQ remapping was enabled on %s but we are not in kdump mode\n",
601+
iommu->name);
602602
clear_ir_pre_enabled(iommu);
603603
iommu_disable_irq_remapping(iommu);
604604
} else if (iommu_load_old_irte(iommu))

0 commit comments

Comments
 (0)