Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 0/3] more dma-buf lockdep priming
Date: Tue, 19 Nov 2019 22:08:41 +0100	[thread overview]
Message-ID: <20191119210844.16947-1-daniel.vetter@ffwll.ch> (raw)

Hi all,

While looking at (dynamic) dma-buf issues and ideas I've spotted a bit
more room for locking down the cross-driver dma_resv rules.

Only functional fallout is a tiny patch for msm, assuming I didn't botch
anything in the auditing of all relevant code.

Comments, review and testing very much appreciated, as usual.

Cheers, Daniel

Daniel Vetter (3):
  drm/modeset: Prime modeset lock vs dma_resv
  dma-resv: Also prime acquire ctx for lockdep
  drm/msm: Don't init ww_mutec acquire ctx before needed

 drivers/dma-buf/dma-resv.c           |  8 +++++++-
 drivers/gpu/drm/drm_mode_config.c    | 28 ++++++++++++++++++++++++++++
 drivers/gpu/drm/msm/msm_gem_submit.c |  2 +-
 3 files changed, 36 insertions(+), 2 deletions(-)

-- 
2.24.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [Intel-gfx] [PATCH 0/3] more dma-buf lockdep priming
Date: Tue, 19 Nov 2019 22:08:41 +0100	[thread overview]
Message-ID: <20191119210844.16947-1-daniel.vetter@ffwll.ch> (raw)
Message-ID: <20191119210841.oO6AQBE_g2cgL1JbMcWnAARw_E2RpaFRFoR7umI_jbI@z> (raw)

Hi all,

While looking at (dynamic) dma-buf issues and ideas I've spotted a bit
more room for locking down the cross-driver dma_resv rules.

Only functional fallout is a tiny patch for msm, assuming I didn't botch
anything in the auditing of all relevant code.

Comments, review and testing very much appreciated, as usual.

Cheers, Daniel

Daniel Vetter (3):
  drm/modeset: Prime modeset lock vs dma_resv
  dma-resv: Also prime acquire ctx for lockdep
  drm/msm: Don't init ww_mutec acquire ctx before needed

 drivers/dma-buf/dma-resv.c           |  8 +++++++-
 drivers/gpu/drm/drm_mode_config.c    | 28 ++++++++++++++++++++++++++++
 drivers/gpu/drm/msm/msm_gem_submit.c |  2 +-
 3 files changed, 36 insertions(+), 2 deletions(-)

-- 
2.24.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-11-19 21:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 21:08 Daniel Vetter [this message]
2019-11-19 21:08 ` [Intel-gfx] [PATCH 0/3] more dma-buf lockdep priming Daniel Vetter
2019-11-19 21:08 ` [PATCH 1/3] drm/modeset: Prime modeset lock vs dma_resv Daniel Vetter
2019-11-19 21:08   ` [Intel-gfx] " Daniel Vetter
2019-11-20  8:34   ` Christian König
2019-11-20  8:34     ` [Intel-gfx] " Christian König
2019-11-20 10:55     ` Daniel Vetter
2019-11-20 10:55       ` [Intel-gfx] " Daniel Vetter
2019-11-19 21:08 ` [PATCH 2/3] dma-resv: Also prime acquire ctx for lockdep Daniel Vetter
2019-11-19 21:08   ` [Intel-gfx] " Daniel Vetter
2019-11-20 11:30   ` Christian König
2019-11-20 11:30     ` [Intel-gfx] " Christian König
2019-11-20 13:56     ` Maarten Lankhorst
2019-11-20 13:56       ` [Intel-gfx] " Maarten Lankhorst
2019-11-19 21:08 ` [PATCH 3/3] drm/msm: Don't init ww_mutec acquire ctx before needed Daniel Vetter
2019-11-19 21:08   ` [Intel-gfx] " Daniel Vetter
     [not found]   ` <20191119210844.16947-4-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2019-11-20  2:07     ` Rob Clark
2019-11-20  2:07       ` [Intel-gfx] " Rob Clark
     [not found]       ` <CAF6AEGuPtwFjM12MRBf_X7GUqJBHt+Xb8vKrT+dddic093Ki6g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-20 10:22         ` Daniel Vetter
2019-11-20 10:22           ` [Intel-gfx] " Daniel Vetter
2019-11-20 10:56   ` [PATCH] " Daniel Vetter
2019-11-20 10:56     ` [Intel-gfx] " Daniel Vetter
     [not found]     ` <20191120105607.3023-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2019-11-21  0:24       ` Rob Clark
2019-11-21  0:24         ` [Intel-gfx] " Rob Clark
2019-11-21 10:03         ` Daniel Vetter
2019-11-21 10:03           ` [Intel-gfx] " Daniel Vetter
2019-11-19 22:31 ` ✗ Fi.CI.CHECKPATCH: warning for more dma-buf lockdep priming Patchwork
2019-11-19 22:31   ` [Intel-gfx] " Patchwork
2019-11-19 22:53 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-19 22:53   ` [Intel-gfx] " Patchwork
2019-11-20 13:55 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-20 13:55   ` [Intel-gfx] " Patchwork
2019-11-20 15:31 ` ✗ Fi.CI.BUILD: failure for more dma-buf lockdep priming (rev2) Patchwork
2019-11-20 15:31   ` [Intel-gfx] " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191119210844.16947-1-daniel.vetter@ffwll.ch \
    --to=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox