[Intel-xe] ✓ CI.checkpatch: success for drm/xe: Fix an invalid locking wait context bug
Patchwork
patchwork at emeril.freedesktop.org
Wed Jul 19 21:07:24 UTC 2023
== Series Details ==
Series: drm/xe: Fix an invalid locking wait context bug
URL : https://patchwork.freedesktop.org/series/121003/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 4c95065af9f4a787ae65e8ed035ad7402e1456bd
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date: Wed Jul 19 15:27:26 2023 -0400
drm/xe: Fix an invalid locking wait context bug
xe_irq_{suspend,resume} were incorrectly using the xe->irq.lock.
The lock was created to protect the gt irq handlers, and not
the irq.enabled. Since suspend/resume and other places touching
irq.enabled are already serialized they don't need protection.
(see other irq.enabled accesses).
Then with this spin lock around xe_irq_reset, we will end up
calling the intel_display_power_is_enabled() function, and
that needs a mutex lock. Hence causing the undesired
"[ BUG: Invalid wait context ]"
Cc: Matthew Auld <matthew.auld at intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch f5459dca41d325590391d4512e937d8ffc2ce126 drm-intel
4c95065af drm/xe: Fix an invalid locking wait context bug
More information about the Intel-xe
mailing list