Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(439)

Side by Side Diff: gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

Issue 362863002: Add future sync point methods to ContextSupport. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 6 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 Name 1 Name
2 2
3 CHROMIUM_sync_point 3 CHROMIUM_sync_point
4 4
5 Name Strings 5 Name Strings
6 6
7 GL_CHROMIUM_sync_point 7 GL_CHROMIUM_sync_point
8 8
9 Version 9 Version
10 10
11 Last Modifed Date: February 25, 2013 11 Last Modifed Date: July 1, 2014
12 12
13 Dependencies 13 Dependencies
14 14
15 OpenGL ES 2.0 is required. 15 OpenGL ES 2.0 is required.
16 16
17 Overview 17 Overview
18 18
19 This extension allows a client to order operations between contexts. 19 This extension allows a client to order operations between contexts.
20 20
21 This extension implements a small subset of ARB_sync, with weaker 21 This extension implements a small subset of ARB_sync, with weaker
(...skipping 19 matching lines...) Expand all
41 uint InsertSyncPointCHROMIUM() 41 uint InsertSyncPointCHROMIUM()
42 42
43 creates a sync point and inserts it into the stream of commands for the 43 creates a sync point and inserts it into the stream of commands for the
44 current context. The sync point acts as a fence, which is signaled when 44 current context. The sync point acts as a fence, which is signaled when
45 previous commands have been submitted to the server, or when the context is 45 previous commands have been submitted to the server, or when the context is
46 destroyed, whichever happens first. The sync point name is returned. The 46 destroyed, whichever happens first. The sync point name is returned. The
47 sync point is implicitly deleted when it becomes signaled. The sync point 47 sync point is implicitly deleted when it becomes signaled. The sync point
48 namespace is shared between all contexts on the same server, including other 48 namespace is shared between all contexts on the same server, including other
49 context groups. 49 context groups.
50 50
51 The command
52
53 uint InsertFutureSyncPointCHROMIUM()
54
55 creates a sync point, but does not insert it into the stream of commands.
56 The returned sync point name can be waited on immediately, but will not be
57 signalled until a retire command is sent, or until the context is
58 destroyed, whichever happens first. This command may only be permitted if
59 a context is "trusted", which is defined by the implementation.
piman 2014/07/11 22:24:32 nit: could we add a static query, or an extension
51 60
52 The command 61 The command
53 62
63 void RetireSyncPointCHROMIUM(uint sync_point)
64
65 causes a sync point to be signaled as soon as the previous commands have
66 been submitted to the server. The sync point named <sync_point> must have
67 been returned by InsertFutureSyncPointCHROMIUM. The sync point name will
68 be implicitly deleted when it becomes signaled. This command may only be
69 permitted if a context is "trusted", which is defined by the
70 implementation.
71
72 The command
73
54 void WaitSyncPointCHROMIUM(uint sync_point) 74 void WaitSyncPointCHROMIUM(uint sync_point)
55 75
56 causes the current context to stop submitting commands until the specified 76 causes the current context to stop submitting commands until the specified
57 sync point becomes signaled. This is implemented as a server-side wait. 77 sync point becomes signaled. This is implemented as a server-side wait.
58 <sync_point> is the name of the sync point to wait for. If <sync_point> 78 <sync_point> is the name of the sync point to wait for. If <sync_point>
59 isn't a valid sync point returned by InsertSyncPointCHROMIUM, or if the sync 79 isn't a valid sync point returned by InsertSyncPointCHROMIUM, or if the sync
60 point has already been deleted, the command is equivalent to a no-op and no 80 point has already been deleted, the command is equivalent to a no-op and no
61 error is generated. 81 error is generated.
62 82
63 Errors 83 Errors
64 84
65 None. 85 None.
66 86
67 New State 87 New State
68 88
69 None. 89 None.
70 90
71 Revision History 91 Revision History
72 92
93 7/1/2014 Added future sync points.
73 2/25/2013 Documented the extension 94 2/25/2013 Documented the extension
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698