From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
david.emett@broadcom.com, thomas.spurden@broadcom.com,
Eric Anholt <eric@anholt.net>
Subject: [PATCH v2 4/5] drm/v3d: Drop reservation of a shared slot in the dma-buf reservations.
Date: Tue, 16 Apr 2019 15:58:55 -0700 [thread overview]
Message-ID: <20190416225856.20264-5-eric@anholt.net> (raw)
In-Reply-To: <20190416225856.20264-1-eric@anholt.net>
We only set the excl (possible-writing) fence pointer and never add a
shared (read-only) fence.
Signed-off-by: Eric Anholt <eric@anholt.net>
---
drivers/gpu/drm/v3d/v3d_gem.c | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/v3d/v3d_gem.c b/drivers/gpu/drm/v3d/v3d_gem.c
index 8bd6fa69f566..6873b14a0d38 100644
--- a/drivers/gpu/drm/v3d/v3d_gem.c
+++ b/drivers/gpu/drm/v3d/v3d_gem.c
@@ -253,18 +253,6 @@ v3d_lock_bo_reservations(struct drm_gem_object **bos,
if (ret)
return ret;
- /* Reserve space for our shared (read-only) fence references,
- * before we commit the CL to the hardware.
- */
- for (i = 0; i < bo_count; i++) {
- ret = reservation_object_reserve_shared(bos[i]->resv, 1);
- if (ret) {
- drm_gem_unlock_reservations(bos, bo_count,
- acquire_ctx);
- return ret;
- }
- }
-
return 0;
}
--
2.20.1
next prev parent reply other threads:[~2019-04-16 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 22:58 [PATCH v2 0/5] V3D CSD support, implicit sync fix Eric Anholt
2019-04-16 22:58 ` [PATCH v2 1/5] drm/v3d: Switch the type of job-> to reduce casting Eric Anholt
2019-04-16 22:58 ` [PATCH v2 2/5] drm/v3d: Refactor job management Eric Anholt
2019-04-16 22:58 ` [PATCH v2 3/5] drm/v3d: Add support for compute shader dispatch Eric Anholt
2019-04-17 21:53 ` Eric Anholt
2019-04-16 22:58 ` Eric Anholt [this message]
2019-04-16 22:58 ` [PATCH v2 5/5] drm/v3d: Add missing implicit synchronization Eric Anholt
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=20190416225856.20264-5-eric@anholt.net \
--to=eric@anholt.net \
--cc=david.emett@broadcom.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=thomas.spurden@broadcom.com \
/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