aboutsummaryrefslogtreecommitdiffstats
path: root/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch
diff options
context:
space:
mode:
Diffstat (limited to 'meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch')
-rw-r--r--meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch51
1 files changed, 51 insertions, 0 deletions
diff --git a/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch
new file mode 100644
index 00000000..13a7e543
--- /dev/null
+++ b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.19.8/2718-drm-amdkfd-Adjust-the-debug-message-in-KFD-ISR.patch
@@ -0,0 +1,51 @@
+From e3cf0566ff081ebae23b1bd40e5dcbf6ca0cb5be Mon Sep 17 00:00:00 2001
+From: Yong Zhao <Yong.Zhao@amd.com>
+Date: Wed, 17 Oct 2018 12:03:48 -0400
+Subject: [PATCH 2718/2940] drm/amdkfd: Adjust the debug message in KFD ISR
+
+This makes debug message get printed even when there is early return.
+
+Signed-off-by: Yong Zhao <Yong.Zhao@amd.com>
+Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
+Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
+Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
+Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
+---
+ drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c | 14 +++++++-------
+ 1 file changed, 7 insertions(+), 7 deletions(-)
+
+diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c b/drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c
+index f836897bbf58..849786492447 100644
+--- a/drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c
++++ b/drivers/gpu/drm/amd/amdkfd/kfd_int_process_v9.c
+@@ -39,20 +39,20 @@ static bool event_interrupt_isr_v9(struct kfd_dev *dev,
+ vmid > dev->vm_info.last_vmid_kfd)
+ return 0;
+
+- /* If there is no valid PASID, it's likely a firmware bug */
+- pasid = SOC15_PASID_FROM_IH_ENTRY(ih_ring_entry);
+- if (WARN_ONCE(pasid == 0, "FW bug: No PASID in KFD interrupt"))
+- return 0;
+-
+ source_id = SOC15_SOURCE_ID_FROM_IH_ENTRY(ih_ring_entry);
+ client_id = SOC15_CLIENT_ID_FROM_IH_ENTRY(ih_ring_entry);
++ pasid = SOC15_PASID_FROM_IH_ENTRY(ih_ring_entry);
+
+- pr_debug("client id 0x%x, source id %d, pasid 0x%x. raw data:\n",
+- client_id, source_id, pasid);
++ pr_debug("client id 0x%x, source id %d, vmid %d, pasid 0x%x. raw data:\n",
++ client_id, source_id, vmid, pasid);
+ pr_debug("%8X, %8X, %8X, %8X, %8X, %8X, %8X, %8X.\n",
+ data[0], data[1], data[2], data[3],
+ data[4], data[5], data[6], data[7]);
+
++ /* If there is no valid PASID, it's likely a firmware bug */
++ if (WARN_ONCE(pasid == 0, "FW bug: No PASID in KFD interrupt"))
++ return 0;
++
+ /* Interrupt types we care about: various signals and faults.
+ * They will be forwarded to a work queue (see below).
+ */
+--
+2.17.1
+