https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240990
Handle the most obvious case of CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID clocks specified directly, using LINUX_CPU_SCHED (that is, kern_clock_gettime()).
Differential D22075
PR240990: linux: handle the CLOCK_{PROCESS,THREAD}_CPUTIME_ID specified directly dchagin on Oct 18 2019, 9:42 AM. Authored by Tags None Referenced Files
Subscribers
Details https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240990 Handle the most obvious case of CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID clocks specified directly, using LINUX_CPU_SCHED (that is, kern_clock_gettime()). Run the test case attached to the PR compiled natively, under linux emulation, and on Debian GNU/Linux (system specs are identical), all results are nearly the same.
Diff Detail
Event TimelineComment Actions Ping? Is there anything left to do here before committing? Did you have a chance to test it with LTP (linux-c7-ltp package)? |