Expose SPDY pushes in DevTools

content/child/resource_dispatcher.cc

Index: content/child/resource_dispatcher.cc
diff --git a/content/child/resource_dispatcher.cc b/content/child/resource_dispatcher.cc
index cbda6c4731052dbe4a471831bd57d203bd4c5e3f..3efa1bd2579f5e998991fa38cb1e685c5313572d 100644
--- a/content/child/resource_dispatcher.cc
+++ b/content/child/resource_dispatcher.cc
@@ -632,6 +632,8 @@ void ResourceDispatcher::ToResourceResponseInfo(
   RemoteToLocalTimeTicks(converter, &load_timing->send_start);
   RemoteToLocalTimeTicks(converter, &load_timing->send_end);
   RemoteToLocalTimeTicks(converter, &load_timing->receive_headers_end);
+  RemoteToLocalTimeTicks(converter, &load_timing->push_start);
+  RemoteToLocalTimeTicks(converter, &load_timing->push_end);

[mmenke, 2016/03/25 14:50:28]

This is somewhat weird...Since renderer process times != browser process times,
we need some conversion.  What this code does is take two known times from the
renderer, two known times from the browser, and a bunch of times between them,
and linearly interpolate those intermediary times from browser to renderer
times.  This mostly works... at least we don't do anything crazy...  *However* 
push_start and push_end can be outside that range, and if a request is fast, we
could have, say, a renderer delta of 100 milliseconds, and a browser delta of 10
milliseconds.  Then interpolation becomes a real source of error here.

Have you thought about this?

   RemoteToLocalTimeTicks(converter, &renderer_info->service_worker_start_time);
   RemoteToLocalTimeTicks(converter, &renderer_info->service_worker_ready_time);