fdo-mirrors/xorg-xorgproto
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/xorg/proto/xorgproto.git synced 2026-05-05 12:18:00 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify role and responsibility for client and server regarding fences

Browse source 
Signed-off-by: Keith Packard <keithp@keithp.com>
This commit is contained in:
Keith Packard 2013-10-19 20:48:04 -07:00
parent 843b6a3118
commit b32994fac6
1 changed files with 13 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
presentproto.txt
View file

@ -169,13 +169,23 @@ The name of this extension is "Present"
When the X server has finished using 'pixmap' for this
operation, it will send a PresentIdleNotify event and arrange
for the 'idle-fence' to be triggered. This may be at any time
for any 'idle-fence' to be triggered. This may be at any time
following the PresentPixmap request -- the contents may be
immediately copied to another buffer, copied just in time for
the vblank interrupt or the pixmap may be used directly for
display (in which case it will be busy until some future
PresentPixmap operation).
If 'idle-fence' is not None, then the client guarantees to the
X server that it will wait for that fence to be signalled
before it uses the pixmap again. If 'idle-fence' is None, then
the X server must arrange for the pixmap to be re-usable by
the client as soon as the PresentIdleNotify event has been
received. Note that if PresentCapabilityFence is set for the
associated CRTC, then clients should use fences to improve
overall systme performance. If PresentCapabilityFence is not
set, then using fences offers no benefit, but also no cost.
If 'target-msc' is greater than the current msc for 'window',
the presentation will occur at (or after) the 'target-msc'
field. Otherwise, the presentation will occur after the next
@ -410,7 +420,8 @@ The name of this extension is "Present"
'pixmap' is the pixmap which is ready for re-use.
'idle-fence' is the fence which is used to synchronize
'idle-fence' is the fence which was provided in the
originating PresentPixmap request and is used to synchronize
rendering between the client and the X server's use of the
buffer. If not None, then the client must wait for the fence
to be signaled before using the pixmap.