Reduce Timer Resolution to 100us with Jitter

RESOLVED FIXED in Firefox 61

Status

()

enhancement
P2
normal
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: tjr, Assigned: tjr)

Tracking

Trunk
mozilla61
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox60+ wontfix, firefox61+ fixed)

Details

Attachments

(2 attachments)

Assignee

Description

a year ago
Given what we know about Spectre Variant attacks - in 60, now that we have Jitter, we can lower the Time Precision back down; we'll match Chrome's at 100 us.
Comment hidden (mozreview-request)
Comment hidden (mozreview-request)
Comment hidden (mozreview-request)

Comment 4

a year ago
mozreview-review
Comment on attachment 8962405 [details]
Bug 1448869 Set Timer Precision to 100 us (with Jitter)

https://reviewboard.mozilla.org/r/231258/#review237016
Attachment #8962405 - Flags: review?(amarchesini) → review+

Comment 5

a year ago
mozreview-review
Comment on attachment 8962477 [details]
Bug 1448869 Turn off jitter for some other wbeaudio tests

https://reviewboard.mozilla.org/r/231304/#review237018
Attachment #8962477 - Flags: review?(amarchesini) → review+
Priority: -- → P2
Assignee

Updated

a year ago
Keywords: checkin-needed

Comment 6

a year ago
Pushed by apavel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed5744c6c5c0
Set Timer Precision to 100 us (with Jitter) r=baku
https://hg.mozilla.org/integration/autoland/rev/fa87fd6d40bc
Turn off jitter for some other wbeaudio tests r=baku
Keywords: checkin-needed

Comment 7

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/ed5744c6c5c0
https://hg.mozilla.org/mozilla-central/rev/fa87fd6d40bc
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
Does this need an uplift request?
Flags: needinfo?(tom)
Assignee

Comment 9

a year ago
It will, but we're reconsidering what the best choice is here.
Flags: needinfo?(tom)
Assignee

Updated

a year ago
Blocks: 1451790
Assignee

Comment 10

a year ago
Superseded by Bug 1451790
You need to log in before you can comment on or make changes to this bug.