diff options
| author | fdoray <fdoray@chromium.org> | 2015-10-30 16:08:34 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-10-30 23:09:26 +0000 |
| commit | 8fe437a06a287010a48833eb657dde801da306a4 (patch) | |
| tree | 13d71b56c3672b5c6ea42e2a7af6aba706f4c74b /remoting/protocol/jingle_session.cc | |
| parent | 55f10fa9e14c0fd6b12ed20cdb27087e9009af7f (diff) | |
| download | chromium_src-8fe437a06a287010a48833eb657dde801da306a4.zip chromium_src-8fe437a06a287010a48833eb657dde801da306a4.tar.gz chromium_src-8fe437a06a287010a48833eb657dde801da306a4.tar.bz2 | |
Generate an ETW event at the end of "Complete" chrome://tracing events.
TraceEventETW export can export chrome://tracing events to ETW.
Unfortunately, the duration of "Complete" is not exported to ETW.
With this CL, an ETW event is exported at the end of "Complete"
chrome://tracing events.
The duration of a chrome://tracing "Complete" event can then be computed
by substracting the timestamp of the an ETW "Complete" event from the
timestamp of the corresponding ETW "Complete End" event.
Also, we can generate a "Region of Interest" in WPA for each "Complete"
event using this definition file (which we could distribute with
UIforETW):
https://drive.google.com/file/d/0B0CFRkIGz7pibWdzQUtpX2NUNGs/view?usp=sharing
BUG=546595
Review URL: https://codereview.chromium.org/1423663011
Cr-Commit-Position: refs/heads/master@{#357214}
Diffstat (limited to 'remoting/protocol/jingle_session.cc')
0 files changed, 0 insertions, 0 deletions