summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/clock_gettime.mdwn2
-rw-r--r--open_issues/dde.mdwn2
-rw-r--r--open_issues/libpthread_CLOCK_MONOTONIC.mdwn2
-rw-r--r--open_issues/performance/io_system/read-ahead.mdwn2
-rw-r--r--open_issues/vdso.mdwn2
5 files changed, 5 insertions, 5 deletions
diff --git a/open_issues/clock_gettime.mdwn b/open_issues/clock_gettime.mdwn
index 5ba6b418..98454d45 100644
--- a/open_issues/clock_gettime.mdwn
+++ b/open_issues/clock_gettime.mdwn
@@ -15,7 +15,7 @@ License|/fdl]]."]]"""]]
Missing `clock_gettime(CLOCK_MONOTONIC)` (e.g. for iceweasel)
It could be a mere matter of extending the
-[[mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]]:
+[[mapped-time_interface|microkernel/mach/gnumach/interface/device/time]]:
add it to
`mapped_time_value_t` in gnumach, handle it in `gnumach/kern/mach_clock.c`, and
make `clock_gettime` use it.
diff --git a/open_issues/dde.mdwn b/open_issues/dde.mdwn
index f0f7cae0..65d84886 100644
--- a/open_issues/dde.mdwn
+++ b/open_issues/dde.mdwn
@@ -394,7 +394,7 @@ After the microkernel devroom at [[community/meetings/FOSDEM_2013]].
<youpi> so ZhengDa preferred to make jiffies a macro which calls a function
which reads the mapped time
-[[Mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]].
+[[Mapped-time_interface|microkernel/mach/gnumach/interface/device/time]].
<youpi> however, that break any use of the work "jiffies", e.g. structure
members & such
diff --git a/open_issues/libpthread_CLOCK_MONOTONIC.mdwn b/open_issues/libpthread_CLOCK_MONOTONIC.mdwn
index 37ee548b..9f732fbe 100644
--- a/open_issues/libpthread_CLOCK_MONOTONIC.mdwn
+++ b/open_issues/libpthread_CLOCK_MONOTONIC.mdwn
@@ -26,7 +26,7 @@ License|/fdl]]."]]"""]]
<pinotree> this way we could add inside hurdtime.c the mapped time stuff
too
-[[Mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]].
+[[Mapped-time_interface|microkernel/mach/gnumach/interface/device/time]].
<pinotree> most probably a noobish question, but why does rt link to
pthread?
diff --git a/open_issues/performance/io_system/read-ahead.mdwn b/open_issues/performance/io_system/read-ahead.mdwn
index 768dca93..cd39328f 100644
--- a/open_issues/performance/io_system/read-ahead.mdwn
+++ b/open_issues/performance/io_system/read-ahead.mdwn
@@ -1324,7 +1324,7 @@ License|/fdl]]."]]"""]]
device_map() -- but IIRC the only one that does (besides mem of course)
is maptime -- which is not a real driver either...
-[[Mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]].
+[[Mapped-time_interface|microkernel/mach/gnumach/interface/device/time]].
<braunr> oh btw, i didn't know you had a blog :)
<antrik> well, it would be possible to replace the device interface by
diff --git a/open_issues/vdso.mdwn b/open_issues/vdso.mdwn
index 2b2d2805..76c43aa8 100644
--- a/open_issues/vdso.mdwn
+++ b/open_issues/vdso.mdwn
@@ -35,7 +35,7 @@ Having vDSO code might be useful for:
* `mach_*_self`: `mach_host_self`, `mach_task_self`, `mach_thread_self`?
- * [[mapped-time_interface|master/microkernel/mach/gnumach/interface/device/time]]
+ * [[mapped-time_interface|microkernel/mach/gnumach/interface/device/time]]
Every application can then use that via the regular
`gettimeofday`/`clock_gettime` and similar calls instead of using the