Bug#716746: marked as done (backport clock_getcpuclockid2 syscall into kfreebsd-9)
Your message dated Mon, 22 Jul 2013 08:50:57 +0200 (CEST)
with message-id <alpine.LNX.2.00.1307220849060.18761@contest.felk.cvut.cz>
and subject line 716746: fixed in kfreebsd-9 9.1-2
has caused the Debian Bug report #716746,
regarding backport clock_getcpuclockid2 syscall into kfreebsd-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
716746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716746
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kfreebsd-9
Severity: wishlist
User: debian-bsd@lists.debian.org
Usertags: kfreebsd
To properly provide CLOCK_THREAD_CPUTIME_ID, CLOCK_PROCESS_CPUTIME_ID
and clock_id's created by clock_getcpuclockid() and
pthread_getcpuclockid(), we need a kernel support.
See also #665287.
The kernel support is available in HEAD (but not in STABLE-9).
It should not be to hard to backport kernel part of
http://www.freebsd.org/cgi/query-pr.cgi?pr=168417
into our kernel.
The FBTL based libpthread will use only this interface,
it will not fallback to TSC timers at all.
The reason is that TSC part is fragile and unaccurate.
Petr
--- End Message ---
--- Begin Message ---
Source: kfreebsd-9
Source-Version: 9.1-2
I verified that this set of patches suffices.
Changes:
kfreebsd-9 (9.1-2) experimental; urgency=low
.
[ Robert Millan ]
* Bump B-D on freebsd-buildutils to 10~svn251967-4.
.
[ Petr Salinger ]
* Build by gcc-4.8,
disable unnecessary 901_disable_optimization_2.diff
* Add 111_ldd_address.diff. Closes: #696556.
* Add backport of CPU-timers support. See #716746.
- 000_cpuclockid2_zombie.diff
- 000_cpuclockid2_syscall.diff
- 000_cpuclockid2_compat32.diff
--- End Message ---
Reply to: