summaryrefslogtreecommitdiff
path: root/include/linux/workqueue_api.h
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2023-05-24 20:56:53 +0300
committerRodrigo Vivi <rodrigo.vivi@intel.com>2023-12-20 02:34:09 +0300
commit565ce72e1c2d540d36ade02e6a7479c4c6a7f2d4 (patch)
treed0ba64cc274b1080fbe01145049af44c7fab7cad /include/linux/workqueue_api.h
parenta2f9f4ff07aac81e80ff1e0913fdbfdde6ba6665 (diff)
downloadlinux-565ce72e1c2d540d36ade02e6a7479c4c6a7f2d4.tar.xz
drm/xe: don't allocate under ct->lock
Seems to be a sensitive lock, where ct->lock looks to be primed with fs_reclaim, so holding that and then allocating memory will cause lockdep to complain. We need to change the ordering wrt to grabbing the ct->lock and potentially grabbing the runtime_pm, since some of the runtime_pm routines can allocate memory (or at least that's what lockdep seems to suggest). Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'include/linux/workqueue_api.h')
0 files changed, 0 insertions, 0 deletions