On Wed, 30 May 2012 21:07:57 +0200, Daniel Vetter <daniel@xxxxxxxx> wrote: > On Wed, May 30, 2012 at 7:41 PM, Eric Anholt <eric@xxxxxxxxxx> 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:
pgpBBu1wDlb0I.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
