|
|
Created:
5 years, 4 months ago by charliea (OOO until 10-5) Modified:
5 years, 3 months ago CC:
chromium-reviews, nduca, jbauman Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMakes TraceTicks use lowres times on Win when highres are buggy or slow
We're doing this so that we can eventually consolidate TraceTicks and
TimeTicks and have one type of timestamp that is reliable, monotonic,
and comparable.
Also, using the high-resolution clock when it's unreliable or slow is
of questionable benefit, as it's easier to make tracing tools
accommodate a coarse timer than one that's unreliable or slow.
BUG=345845
Committed: https://crrev.com/d26a96920910558328b0d6e50af72ccde3a1e625
Cr-Commit-Position: refs/heads/master@{#345449}
Patch Set 1 #Patch Set 2 : #
Total comments: 1
Patch Set 3 : Removed g_system_trace_now_function #
Total comments: 2
Patch Set 4 : Improved the comments about why we're changing timer behavior #Messages
Total messages: 40 (14 generated)
charliea@chromium.org changed reviewers: + fmeawad@google.com
Hi Fadi, Would you mind doing a pre-review of this CL?
fmeawad@chromium.org changed reviewers: + fmeawad@chromium.org
https://codereview.chromium.org/1284053004/diff/20001/base/time/time_win.cc File base/time/time_win.cc (right): https://codereview.chromium.org/1284053004/diff/20001/base/time/time_win.cc#n... base/time/time_win.cc:451: now_function = system_trace_now_function = &RolloverProtectedNow; Can you explain why you still need 2 variable (now_function and system_trace_now_function)
On 2015/08/21 21:24:40, fmeawad wrote: > https://codereview.chromium.org/1284053004/diff/20001/base/time/time_win.cc > File base/time/time_win.cc (right): > > https://codereview.chromium.org/1284053004/diff/20001/base/time/time_win.cc#n... > base/time/time_win.cc:451: now_function = system_trace_now_function = > &RolloverProtectedNow; > Can you explain why you still need 2 variable (now_function and > system_trace_now_function) You're absolutely right - I don't. Went ahead and removed g_system_trace_now_function altogether.
fmeawad@chromium.org changed reviewers: - fmeawad@google.com
lg 2 me
charliea@chromium.org changed reviewers: + nduca@chromium.org
charliea@chromium.org changed reviewers: + brianderson@chromium.org - nduca@chromium.org
+r:brianderson -r:nduca +cc:nduca
nduca@chromium.org changed reviewers: + nduca@chromium.org
lgtm but lets go with brian for the main review
charliea@chromium.org changed reviewers: + miu@chromium.org
+r:miu (at brianderson's suggestion)
lgtm too
lgtm
The CQ bit was checked by charliea@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1284053004/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1284053004/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
charliea@chromium.org changed reviewers: + jam@chromium.org
+R:jam for OWNERS
On 2015/08/25 14:01:57, charliea wrote: > +R:jam for OWNERS please use an owner from base/
charliea@chromium.org changed reviewers: + danakj@chromium.org - jam@chromium.org
+R: danakj -R:jam
https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc File base/time/time_win.cc (right): https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc#n... base/time/time_win.cc:445: NowFunction now_function; Can you add comments saying that TraceTicks::Now() will always use the same timer as TimeTicks::Now() and why that is okay/good/better even in the case where the QPC is expensive/unreliable? It would also be nice to add such comment to the CL description too.
On 2015/08/25 18:37:53, danakj wrote: > https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc > File base/time/time_win.cc (right): > > https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc#n... > base/time/time_win.cc:445: NowFunction now_function; > Can you add comments saying that TraceTicks::Now() will always use the same > timer as TimeTicks::Now() and why that is okay/good/better even in the case > where the QPC is expensive/unreliable? > > It would also be nice to add such comment to the CL description too. Sorry about that - I should have given you more context (and had comments doing the same) in the first place.
https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc File base/time/time_win.cc (right): https://codereview.chromium.org/1284053004/diff/40001/base/time/time_win.cc#n... base/time/time_win.cc:445: NowFunction now_function; On 2015/08/25 18:37:53, danakj wrote: > Can you add comments saying that TraceTicks::Now() will always use the same > timer as TimeTicks::Now() and why that is okay/good/better even in the case > where the QPC is expensive/unreliable? > > It would also be nice to add such comment to the CL description too. Done.
LGTM
+jbauman fyi
The CQ bit was checked by charliea@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from brianderson@chromium.org, nduca@chromium.org, miu@chromium.org Link to the patchset: https://codereview.chromium.org/1284053004/#ps60001 (title: "Improved the comments about why we're changing timer behavior")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1284053004/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1284053004/60001
Message was sent while issue was closed.
Committed patchset #4 (id:60001)
Message was sent while issue was closed.
Patchset 4 (id:??) landed as https://crrev.com/d26a96920910558328b0d6e50af72ccde3a1e625 Cr-Commit-Position: refs/heads/master@{#345449}
Message was sent while issue was closed.
thakis@chromium.org changed reviewers: + thakis@chromium.org
Message was sent while issue was closed.
This broke the clang/win build: ..\..\base\time\time_win.cc(383,11) : error: unused function 'InitialSystemTraceNowFunction' [-Werror,-Wunused-function] TimeDelta InitialSystemTraceNowFunction(); ^ 1 error generated. Can you fix, please?
Message was sent while issue was closed.
On 2015/08/25 22:23:50, Nico wrote: > This broke the clang/win build: > > ..\..\base\time\time_win.cc(383,11) : error: unused function > 'InitialSystemTraceNowFunction' [-Werror,-Wunused-function] > TimeDelta InitialSystemTraceNowFunction(); > ^ > 1 error generated. > > Can you fix, please? Nevermind, got it: https://codereview.chromium.org/1312313002
Message was sent while issue was closed.
On 2015/08/25 22:26:00, Nico wrote: > On 2015/08/25 22:23:50, Nico wrote: > > This broke the clang/win build: > > > > ..\..\base\time\time_win.cc(383,11) : error: unused function > > 'InitialSystemTraceNowFunction' [-Werror,-Wunused-function] > > TimeDelta InitialSystemTraceNowFunction(); > > ^ > > 1 error generated. > > > > Can you fix, please? > > Nevermind, got it: https://codereview.chromium.org/1312313002 Sorry about that Nico. |