drm/xe: Move xe_ggtt_invalidate out from ggtt->lock
authorMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
Wed, 6 Mar 2024 05:20:02 +0000 (21:20 -0800)
committerMaarten Lankhorst <maarten.lankhorst@linux.intel.com>
Wed, 20 Mar 2024 09:49:14 +0000 (10:49 +0100)
commita825cef2e793f085a3d0443c3843da7f81af80cb
tree8d9ae22fc7a2f5dac065ee98c81003a9d2c01206
parent231c4110873a5db4975512c30aa10edcc5be56e2
drm/xe: Move xe_ggtt_invalidate out from ggtt->lock

Considering the caller of the GGTT functions should keep the
backing storage alive before the function completes, it's not
necessary to invalidate with the GGTT lock held. This just adds
latency for every user of the GGTT.

Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20240306052002.311196-5-matthew.brost@intel.com
drivers/gpu/drm/xe/xe_ggtt.c