From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: mesa-dev@lists.freedesktop.org, Ben Widawsky <ben@bwidawsk.net>,
dri-devel@lists.freedesktop.org
Subject: Re: Fw: [Intel-gfx] [PATCH] intel: add a timed wait function
Date: Wed, 30 May 2012 15:35:35 -0700 [thread overview]
Message-ID: <8762bds3ew.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <CAKMK7uEPBjKkTC+4NqS7yFHxE1ju7902v+Lk_TEojy196CvJnw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 943 bytes --]
On Wed, 30 May 2012 21:07:57 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, May 30, 2012 at 7:41 PM, Eric Anholt <eric@anholt.net> wrote:
> > I guess GL_ALREADY_SIGNALED handling will be done using a check for
> > bo_busy() before calling this.
>
> I've just read through the mesa code and gl_already_signalled seems to
> be handled already by core mesa code in _mesa_ClientWaitSync (if the
> driver sets syncObject->Status correctly). So I guess the current
> kernel code should work as-is and only the libdrm interface needs some
> colour adjustments around the timeout parameter.
Yeah, matches what I found.
Did you want pointer for timeout in the userspace api? I don't feel
strongly about it, I just didn't see a use. The equivalent API I could
think of was select(), where apparently linux returns time unwaited,
while "everyone else" doesn't. I don't see a strong recommendation
either way from that.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-05-30 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 20:16 Fw: [Intel-gfx] [PATCH] intel: add a timed wait function Ben Widawsky
2012-05-30 17:41 ` Eric Anholt
2012-05-30 18:13 ` Ben Widawsky
2012-05-30 19:07 ` Fw: " Daniel Vetter
2012-05-30 20:32 ` Ben Widawsky
2012-05-30 22:35 ` Eric Anholt [this message]
2012-05-31 7:05 ` Fw: " 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=8762bds3ew.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=ben@bwidawsk.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@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 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.