aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGary R Hook <gary.hook@amd.com>2017-12-20 09:47:07 -0700
committerAlex Williamson <alex.williamson@redhat.com>2017-12-20 09:47:07 -0700
commitf9fc049ef1e05da3e3d2a45d098ec89b89bf687e (patch)
tree0a77ce431501bf0d4957b44f1add53be44fd278c
parentLinux 4.15-rc4 (diff)
downloadlinux-dev-f9fc049ef1e05da3e3d2a45d098ec89b89bf687e.tar.xz
linux-dev-f9fc049ef1e05da3e3d2a45d098ec89b89bf687e.zip
iommu/amd - Record more information about unknown events
When an unknown type event occurs, the default information written to the syslog should dump raw event data. This could provide insight into the event that occurred. Signed-off-by: Gary R Hook <gary.hook@amd.com> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
-rw-r--r--drivers/iommu/amd_iommu.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index 7d5eb004091d..6af7ae6eac5e 100644
--- a/drivers/iommu/amd_iommu.c
+++ b/drivers/iommu/amd_iommu.c
@@ -616,7 +616,9 @@ retry:
address, flags);
break;
default:
- printk(KERN_ERR "UNKNOWN type=0x%02x]\n", type);
+ printk(KERN_ERR "UNKNOWN type=0x%02x event[0]=0x%08x "
+ "event[1]=0x%08x event[2]=0x%08x event[3]=0x%08x\n",
+ type, event[0], event[1], event[2], event[3]);
}
memset(__evt, 0, 4 * sizeof(u32));