SetNeedsRedraw directly when updating a visible tile.

cc/test/thread_blocker.h

+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CC_TEST_THREAD_BLOCKER_H_
+#define CC_TEST_THREAD_BLOCKER_H_
+
+#include "base/synchronization/lock.h"
+#include "base/synchronization/waitable_event.h"
+
+namespace cc {
+
+// This class will block inside the Wait() function after BlockWait() has been
+// called until UnblockWait() is called. Because Wait() blocks, the
+// UnblockWait() call must be done from another thread, so this class is safe to
+// use on multiple threads.
+class ThreadBlocker {

[reveman, 2014/11/13 20:10:04]

What's the difference between an instance of this class and a
base::WaitableEvent instance that is initially in signaled state?

[danakj, 2014/11/13 20:14:17]

A nicer API around should_delay_ I think for this use case.

[danakj, 2014/11/13 20:20:18]

Mmm, I guess the test could Reset() instead of BlockWait() and Signal() instead
of UnblockWait(). I could at least get rid of the should_delay_ bool and the
lock I guess... and then it looks just like WaitableEvent, heh. Guess I should
just use that.

+ public:
+  ThreadBlocker();
+  ~ThreadBlocker();
+
+  // This will block if BlockWait() has been called until UnblockWait() is
+  // called.
+  void Wait();
+
+  // Makes future calls to Wait() block.
+  void BlockWait();
+  // Unblocks any current calls to Wait() and prevents future calls from
+  // blocking.
+  void UnblockWait();
+
+ private:
+  base::Lock lock_;
+  bool should_delay_;
+  base::WaitableEvent waiter_;
+
+  DISALLOW_COPY_AND_ASSIGN(ThreadBlocker);
+};
+
+}  // namespace cc
+
+#endif  // CC_TEST_THREAD_BLOCKER_H_