[Intel-gfx] [PATCH 05/26] drm/i915: Remove locking from i915_gem_object_prepare_read/write

[Thomas Hellström (Intel)]

On 6/23/20 4:28 PM, Maarten Lankhorst wrote:
> Execbuffer submission will perform its own WW locking, and we
> cannot rely on the implicit lock there.
>
> This also makes it clear that the GVT code will get a lockdep splat when
> multiple batchbuffer shadows need to be performed in the same instance,
> fix that up.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
> ---
>   drivers/gpu/drm/i915/gem/i915_gem_domain.c    | 20 ++++++-------------
>   .../gpu/drm/i915/gem/i915_gem_execbuffer.c    | 13 ++++++++++--
>   drivers/gpu/drm/i915/gem/i915_gem_object.h    |  1 -
>   .../gpu/drm/i915/gem/selftests/huge_pages.c   |  5 ++++-
>   .../i915/gem/selftests/i915_gem_coherency.c   | 14 +++++++++----
>   .../drm/i915/gem/selftests/i915_gem_context.c | 12 ++++++++---
>   drivers/gpu/drm/i915/gvt/cmd_parser.c         |  1 +
>   drivers/gpu/drm/i915/i915_gem.c               | 20 +++++++++++++++++--
>   8 files changed, 59 insertions(+), 27 deletions(-)
>
ltgm. Reviewed-by: Thomas Hellström <thomas.hellstrom at intel.com>