提交 1d4471b1 编写于 作者: R Rich Felker

sched_rr_get_interval: don't assume time_t is 32-bit on 32-bit archs

as with clock_getres, the time64 syscall for this is not necessary or
useful, this time since scheduling timeslices are not on the order 68
years. if there's a 32-bit syscall, use it and expand the result into
timespec; otherwise there is only one syscall and it does the right
thing to store to timespec directly.

on 64-bit archs, there is no change to the code after preprocessing.
上级 24485855
...@@ -3,5 +3,19 @@ ...@@ -3,5 +3,19 @@
int sched_rr_get_interval(pid_t pid, struct timespec *ts) int sched_rr_get_interval(pid_t pid, struct timespec *ts)
{ {
#ifdef SYS_sched_rr_get_interval_time64
/* On a 32-bit arch, use the old syscall if it exists. */
if (SYS_sched_rr_get_interval != SYS_sched_rr_get_interval_time64) {
long ts32[2];
int r = __syscall(SYS_sched_rr_get_interval, pid, ts32);
if (!r) {
ts->tv_sec = ts32[0];
ts->tv_nsec = ts32[1];
}
return __syscall_ret(r);
}
#endif
/* If reaching this point, it's a 64-bit arch or time64-only
* 32-bit arch and we can get result directly into timespec. */
return syscall(SYS_sched_rr_get_interval, pid, ts); return syscall(SYS_sched_rr_get_interval, pid, ts);
} }
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册