1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
module ProcessSpecs
def self.clock_constants
clocks = []
platform_is_not :windows, :solaris do
clocks += Process.constants.select { |c| c.to_s.start_with?('CLOCK_') }
# These require CAP_WAKE_ALARM and are not documented in
# Process#clock_gettime. They return EINVAL if the permission
# is not granted.
clocks -= [:CLOCK_BOOTTIME_ALARM, :CLOCK_REALTIME_ALARM]
end
clocks.sort.map { |c|
[c, Process.const_get(c)]
}
end
def self.clock_constants_for_resolution_checks
clocks = clock_constants
# These clocks in practice on Linux do not seem to match their reported resolution.
platform_is :linux do
clocks = clocks.reject { |clock, value|
[:CLOCK_REALTIME_COARSE, :CLOCK_MONOTONIC_COARSE].include?(clock)
}
end
# These clocks in practice on macOS seem to be less precise than advertised by clock_getres
platform_is :darwin do
clocks = clocks.reject { |clock, value|
[:CLOCK_UPTIME_RAW_APPROX, :CLOCK_MONOTONIC_RAW_APPROX].include?(clock)
}
end
# These clocks in practice on ARM on Linux do not seem to match their reported resolution.
platform_is :armv7l, :aarch64 do
clocks = clocks.reject { |clock, value|
[:CLOCK_PROCESS_CPUTIME_ID, :CLOCK_THREAD_CPUTIME_ID, :CLOCK_MONOTONIC_RAW].include?(clock)
}
end
# These clocks in practice on AIX seem to be more precise than their reported resolution.
platform_is :aix do
clocks = clocks.reject { |clock, value|
[:CLOCK_REALTIME, :CLOCK_MONOTONIC].include?(clock)
}
end
# On a Hyper-V Linux guest machine, these clocks in practice
# seem to be less precise than advertised by clock_getres
platform_is :linux do
clocks = clocks.reject { |clock, value|
clock == :CLOCK_MONOTONIC_RAW
}
end
clocks
end
end
|
