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
|
[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!meta title="clock_gettime"]]
[[!tag open_issue_glibc open_issue_gnumach]]
Missing `clock_gettime(CLOCK_MONOTONIC)` (e.g. for iceweasel)
It could be a mere matter of extending the mappable clock: add it to
`mapped_time_value_t` in gnumach, handle it in `gnumach/kern/mach_clock.c`, and
make `clock_gettime` use it.
BTW, also make `gettimeofday()` use it, since it's way more efficient and some
applications assume that it is.
What about adding a nanosecond-precision clock, too? --[[tschwinge]]
IRC, freenode, #hurd, 2011-08-26:
< pinotree> youpi: thing is: apparently i found a simple way to have a
monotonic clock as mmap-able device inside gnumach
< pinotree> currently, in kern/mach_clock.c there's a variable 'time',
which gets increased on clock interrupt, and optionally modified by
host_set_time
< pinotree> ()
< pinotree> if i add a new variable next to it, only increasing it on
interrupt but not modifying it at all otherwise, would that give me a
monotonic clock?
< pinotree> at least on sme basic tests i did, it seems it could work that
way
< youpi> yes, it should work
< braunr> sure
< youpi> and that's the way I was considering implementing it
|
