diff options
| author | Lu Baolu <[email protected]> | 2024-07-02 21:08:36 +0800 |
|---|---|---|
| committer | Will Deacon <[email protected]> | 2024-07-03 16:39:26 +0100 |
| commit | 804f98e224e41c16e3b70f97790f84894745a392 (patch) | |
| tree | 51fdaaaebb6fb1414c44f4a936ffa19d1be5fe0d /lib/test_fortify/write_overflow-strscpy.c | |
| parent | e995fcde6070f0981e083c1e2e17e401e6c17ad9 (diff) | |
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]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strscpy.c')
0 files changed, 0 insertions, 0 deletions