Confirmed users
346
edits
Project Silk: Difference between revisions
→Order to dispatch Vsync events
No edit summary |
|||
| Line 39: | Line 39: | ||
Note: We need to wait the APZC processed the input event in step 1, then do the remaining task. We might have a large delay for context switch. | Note: We need to wait the APZC processed the input event in step 1, then do the remaining task. We might have a large delay for context switch. | ||
The APZ event processing code all currently runs on the main thread. We need that to run to completion, and forward any required input events to the child processes before we send the vsync notification that will trigger the refresh driver. Thus, we will have the most up to date touch coordinates rather than have a racy condition where we might process the previous touch event versus the latest touch events when we composite. [https://bugzilla.mozilla.org/show_bug.cgi?id=930939 Bug 930939] will do the APZ off the main thread(it will update the APZ at VsyncDispatcher thread). | |||
[[File:Vsync_Threads_Context_Switch.jpg|800px|Project Silk architecture]] | [[File:Vsync_Threads_Context_Switch.jpg|800px|Project Silk architecture]] | ||