From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] consistently use dma_resv locking wrappers
Date: Tue, 3 Dec 2019 17:43:52 +0100 [thread overview]
Message-ID: <20191203164352.GD624164@phenom.ffwll.local> (raw)
In-Reply-To: <20191125094356.161941-1-daniel.vetter@ffwll.ch>
On Mon, Nov 25, 2019 at 10:43:52AM +0100, Daniel Vetter wrote:
> Hi all,
>
> This is prep work for some dma_resv series I'm tinkering with, but I
> figured good to split this out since good idea to land this no matter what
> exactly I'll end up creating in dma_resv. With these everything in
> drivers/gpu nicely goes through either the dma_resv or drm_modeset_lock
> wrappers, and doesn't call ww_mutex directly.
>
> Review, comments, acks all very much welcome, as usual.
>
> Cheers, Daniel
>
> Daniel Vetter (4):
> drm/etnaviv: Use dma_resv locking wrappers
> drm/i915: Use dma_resv locking wrappers
> drm/msm: Use dma_resv locking wrappers
> drm/vc4: Use dma_resv locking wrappers
Ping for some review/acks on this series ...
-Daniel
>
> drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 8 +++-----
> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 6 +++---
> drivers/gpu/drm/msm/msm_gem_submit.c | 10 +++++-----
> drivers/gpu/drm/vc4/vc4_gem.c | 11 +++++------
> 4 files changed, 16 insertions(+), 19 deletions(-)
>
> --
> 2.24.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 0/4] consistently use dma_resv locking wrappers
Date: Tue, 3 Dec 2019 17:43:52 +0100 [thread overview]
Message-ID: <20191203164352.GD624164@phenom.ffwll.local> (raw)
In-Reply-To: <20191125094356.161941-1-daniel.vetter@ffwll.ch>
On Mon, Nov 25, 2019 at 10:43:52AM +0100, Daniel Vetter wrote:
> Hi all,
>
> This is prep work for some dma_resv series I'm tinkering with, but I
> figured good to split this out since good idea to land this no matter what
> exactly I'll end up creating in dma_resv. With these everything in
> drivers/gpu nicely goes through either the dma_resv or drm_modeset_lock
> wrappers, and doesn't call ww_mutex directly.
>
> Review, comments, acks all very much welcome, as usual.
>
> Cheers, Daniel
>
> Daniel Vetter (4):
> drm/etnaviv: Use dma_resv locking wrappers
> drm/i915: Use dma_resv locking wrappers
> drm/msm: Use dma_resv locking wrappers
> drm/vc4: Use dma_resv locking wrappers
Ping for some review/acks on this series ...
-Daniel
>
> drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 8 +++-----
> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 6 +++---
> drivers/gpu/drm/msm/msm_gem_submit.c | 10 +++++-----
> drivers/gpu/drm/vc4/vc4_gem.c | 11 +++++------
> 4 files changed, 16 insertions(+), 19 deletions(-)
>
> --
> 2.24.0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-03 16:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 9:43 [PATCH 0/4] consistently use dma_resv locking wrappers Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-11-25 9:43 ` [PATCH 1/4] drm/etnaviv: Use " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 20:08 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:52 ` Ruhl, Michael J
2019-12-13 20:52 ` [Intel-gfx] " Ruhl, Michael J
2019-12-14 0:09 ` [PATCH] " Daniel Vetter
2019-12-16 14:29 ` Ruhl, Michael J
2019-12-16 15:14 ` Lucas Stach
2019-12-17 13:03 ` Daniel Vetter
2019-11-25 9:43 ` [PATCH 2/4] drm/i915: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-12-14 0:10 ` Daniel Vetter
2019-12-14 0:10 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` [PATCH 3/4] drm/msm: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 20:08 ` [Intel-gfx] " Daniel Vetter
2019-12-13 20:08 ` Daniel Vetter
2019-12-13 21:43 ` Eric Anholt
2019-12-13 21:43 ` [Intel-gfx] " Eric Anholt
2019-12-13 21:43 ` Eric Anholt
2019-11-25 9:43 ` [PATCH 4/4] drm/vc4: " Daniel Vetter
2019-11-25 9:43 ` [Intel-gfx] " Daniel Vetter
2019-11-25 9:43 ` Daniel Vetter
2019-12-13 20:10 ` Daniel Vetter
2019-12-13 20:10 ` [Intel-gfx] " Daniel Vetter
2019-12-13 21:40 ` Eric Anholt
2019-12-13 21:40 ` [Intel-gfx] " Eric Anholt
2019-11-25 11:55 ` ✗ Fi.CI.CHECKPATCH: warning for consistently use " Patchwork
2019-11-25 11:55 ` [Intel-gfx] " Patchwork
2019-11-25 12:20 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-25 12:20 ` [Intel-gfx] " Patchwork
2019-12-03 16:43 ` Daniel Vetter [this message]
2019-12-03 16:43 ` [Intel-gfx] [PATCH 0/4] " Daniel Vetter
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=20191203164352.GD624164@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.