Adds a didReceiveInputEvent api to the blink scheduler

Input tasks are not always routed by the main thread, but the
blink scheduler still needs to know about them because we
want it to enter low latency mode when the user is
interacting with the device.  To facilitate that this patch
adds an didReceiveInputEvent API function.

BUG=391005
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181830

[alexclarke, 2014-09-10 15:07:32]

alexclarke@google.com changed reviewers:
+ skyostil@chromium.org

[alexclarke, 2014-09-10 15:08:02]

alexclarke@google.com changed reviewers:
+ alexclarke@google.com, eseidel@chromium.org

[eseidel, 2014-09-10 16:10:34]

lgtm

So long as we're not taking that lock too often (couple times a frame seems
fine).

https://codereview.chromium.org/554693004/diff/20001/Source/platform/schedule...
File Source/platform/scheduler/Scheduler.cpp (right):

https://codereview.chromium.org/554693004/diff/20001/Source/platform/schedule...
Source/platform/scheduler/Scheduler.cpp:165: void
Scheduler::didReceiveInputEvent()
How often is this called?

[Sami, 2014-09-11 15:12:05]

lgtm. One question about the unit tests though.

https://codereview.chromium.org/554693004/diff/60001/Source/platform/schedule...
File Source/platform/scheduler/SchedulerTest.cpp (right):

https://codereview.chromium.org/554693004/diff/60001/Source/platform/schedule...
Source/platform/scheduler/SchedulerTest.cpp:489:
m_scheduler->postCompositorTask(FROM_HERE, WTF::bind(&dummyTask));
This problem was here already before, but should be call runPendingTasks() in
TearDown() to make sure tasks don't leak from one test to another?

[alexclarke, 2014-09-11 15:21:12]

https://codereview.chromium.org/554693004/diff/20001/Source/platform/schedule...
File Source/platform/scheduler/Scheduler.cpp (right):

https://codereview.chromium.org/554693004/diff/20001/Source/platform/schedule...
Source/platform/scheduler/Scheduler.cpp:165: void
Scheduler::didReceiveInputEvent()
On 2014/09/10 16:10:34, eseidel wrote:
> How often is this called?

At most a handful of times per frame.

https://codereview.chromium.org/554693004/diff/60001/Source/platform/schedule...
File Source/platform/scheduler/SchedulerTest.cpp (right):

https://codereview.chromium.org/554693004/diff/60001/Source/platform/schedule...
Source/platform/scheduler/SchedulerTest.cpp:489:
m_scheduler->postCompositorTask(FROM_HERE, WTF::bind(&dummyTask));
On 2014/09/11 15:12:05, Sami wrote:
> This problem was here already before, but should be call runPendingTasks() in
> TearDown() to make sure tasks don't leak from one test to another?

Done.

[alexclarke, 2014-09-11 15:21:24]

The CQ bit was checked by alexclarke@google.com

[commit-bot: I haz the power, 2014-09-11 15:22:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/554693004/80001

[commit-bot: I haz the power, 2014-09-11 15:39:19]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-11 15:39:20]

Try jobs failed on following builders:
  linux_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/linux_blink_rel/builds/2...)

[alexclarke, 2014-09-11 15:50:39]

The CQ bit was checked by alexclarke@google.com

[commit-bot: I haz the power, 2014-09-11 15:51:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/554693004/100001

[commit-bot: I haz the power, 2014-09-11 16:54:33]

Committed patchset #6 (id:100001) as 181830