From: Ben Widawsky <ben@bwidawsk.net>
To: Mesa dev <mesa-dev@lists.freedesktop.org>
Cc: Ben Widawsky <ben@bwidawsk.net>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: [RFC] [PATCH] i965: better ClientWaitSync
Date: Thu, 7 Jun 2012 09:12:42 -0700 [thread overview]
Message-ID: <1339085562-7358-2-git-send-email-ben@bwidawsk.net> (raw)
In-Reply-To: <1339085562-7358-1-git-send-email-ben@bwidawsk.net>
Use the new libdrm functionality to actually do timed waits on the sync
object.
This patch is missing the configure.ac update to check for the correct
libdrm supporting this function. As of now, libdrm has not yet received
the version bump. That's mostly why this patch is "RFC"
Since intel_client_wait_sync function previously had no way of reporting
back the errors/timeouts, and I do not have a good test case anyway,
I've decided to not worry about this also.
Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
---
src/mesa/drivers/dri/intel/intel_syncobj.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/intel/intel_syncobj.c b/src/mesa/drivers/dri/intel/intel_syncobj.c
index b303ea8..4dd8b7b 100644
--- a/src/mesa/drivers/dri/intel/intel_syncobj.c
+++ b/src/mesa/drivers/dri/intel/intel_syncobj.c
@@ -93,7 +93,7 @@ static void intel_client_wait_sync(struct gl_context *ctx, struct gl_sync_object
struct intel_sync_object *sync = (struct intel_sync_object *)s;
if (sync->bo) {
- drm_intel_bo_wait_rendering(sync->bo);
+ drm_intel_gem_bo_wait(sync->bo, timeout);
s->StatusFlag = 1;
drm_intel_bo_unreference(sync->bo);
sync->bo = NULL;
--
1.7.10.3
next prev parent reply other threads:[~2012-06-07 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 16:12 [PATCH v5] intel: wait render timeout implementation Ben Widawsky
2012-06-07 16:12 ` Ben Widawsky [this message]
2012-06-07 19:08 ` [RFC] [PATCH] i965: better ClientWaitSync Daniel Vetter
2012-06-07 20:23 ` Ben Widawsky
2012-06-08 18:19 ` [PATCH v5] intel: wait render timeout implementation 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=1339085562-7358-2-git-send-email-ben@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mesa-dev@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