diff options
| author |   Qiuxu Zhuo <qiuxu.zhuo@intel.com> | 2017-04-28 01:16:15 +0800 |
|---|---|---|
| committer |   Joerg Roedel <jroedel@suse.de> | 2017-04-28 23:38:42 +0200 |
| commit | 8e12188400668046870087fc278404a11c853061 (patch) | |
| tree | 6f810ea86232716d68047539aba4819eb7befb9e /Documentation/devicetree/bindings | |
| parent | x86, iommu/vt-d: Add an option to disable Intel IOMMU force on (diff) | |
| download | linux-dev-8e12188400668046870087fc278404a11c853061.tar.xz linux-dev-8e12188400668046870087fc278404a11c853061.zip | |
iommu/vt-d: Don't print the failure message when booting non-kdump kernel
When booting a new non-kdump kernel, we have below failure message:
[ 0.004000] DMAR-IR: IRQ remapping was enabled on dmar2 but we are not in kdump mode
[ 0.004000] DMAR-IR: Failed to copy IR table for dmar2 from previous kernel
[ 0.004000] DMAR-IR: IRQ remapping was enabled on dmar1 but we are not in kdump mode
[ 0.004000] DMAR-IR: Failed to copy IR table for dmar1 from previous kernel
[ 0.004000] DMAR-IR: IRQ remapping was enabled on dmar0 but we are not in kdump mode
[ 0.004000] DMAR-IR: Failed to copy IR table for dmar0 from previous kernel
[ 0.004000] DMAR-IR: IRQ remapping was enabled on dmar3 but we are not in kdump mode
[ 0.004000] DMAR-IR: Failed to copy IR table for dmar3 from previous kernel
For non-kdump case, we no need to copy IR table from previous kernel
so it's nonthing actually failed. To be less alarming or misleading,
do not print "DMAR-IR: Failed to copy IR table for dmar[0-9] from
previous kernel" messages when booting non-kdump kernel.
Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'Documentation/devicetree/bindings')
0 files changed, 0 insertions, 0 deletions