path: root/open_issues/clock_gettime.mdwn
diff options
authorThomas Schwinge <>2013-04-07 18:28:11 +0200
committerThomas Schwinge <>2013-04-07 18:28:11 +0200
commit325d3600adae1a2da62f9a24ac34ad2b47a22f97 (patch)
treef0637c13c8aec0d0793f7d2498f5e2237e693c4b /open_issues/clock_gettime.mdwn
parentacab07dfc9df44d6d54e03c701a90b5d6f537fcd (diff)
parent6c7d45e4631784d0e077e806521a736da6b0266e (diff)
Merge remote-tracking branch 'fp/master'
Conflicts: hurd.mdwn hurd/debugging/rpctrace.mdwn open_issues/clock_gettime.mdwn open_issues/time.mdwn
Diffstat (limited to 'open_issues/clock_gettime.mdwn')
1 files changed, 9 insertions, 0 deletions
diff --git a/open_issues/clock_gettime.mdwn b/open_issues/clock_gettime.mdwn
index 3caa6c28..5ba6b418 100644
--- a/open_issues/clock_gettime.mdwn
+++ b/open_issues/clock_gettime.mdwn
@@ -188,4 +188,13 @@ In context of [[select]].
<youpi> and we'll make that a 64bit struct when we have a64bit userland
+# IRC, freenode, #hurd, 2013-04-06
+ <tschwinge> pinotree: You had once been working on adding nsec-procision
+ timestamps to GNU Mach's maptime interface (or what the name is). Is
+ that blocked on something or just waiting to be continued?
+ <pinotree> blocked on me needing to learn more the proper way to do
+ "atomic" update of the struct with time :)
# Candidate for [[vDSO]] code?