2011-02-12 05:22:29 +00:00
|
|
|
#ifndef _SCHED_H
|
|
|
|
#define _SCHED_H
|
|
|
|
#ifdef __cplusplus
|
|
|
|
extern "C" {
|
|
|
|
#endif
|
|
|
|
|
2012-09-08 03:13:55 +00:00
|
|
|
#include <features.h>
|
|
|
|
|
2011-02-12 05:22:29 +00:00
|
|
|
#define __NEED_struct_timespec
|
|
|
|
#define __NEED_pid_t
|
|
|
|
#define __NEED_time_t
|
|
|
|
|
|
|
|
#include <bits/alltypes.h>
|
|
|
|
|
|
|
|
struct sched_param {
|
|
|
|
int sched_priority;
|
|
|
|
int sched_ss_low_priority;
|
|
|
|
struct timespec sched_ss_repl_period;
|
|
|
|
struct timespec sched_ss_init_budget;
|
|
|
|
int sched_ss_max_repl;
|
|
|
|
};
|
|
|
|
|
|
|
|
int sched_get_priority_max(int);
|
|
|
|
int sched_get_priority_min(int);
|
|
|
|
int sched_getparam(pid_t, struct sched_param *);
|
|
|
|
int sched_getscheduler(pid_t);
|
|
|
|
int sched_rr_get_interval(pid_t, struct timespec *);
|
|
|
|
int sched_setparam(pid_t, const struct sched_param *);
|
|
|
|
int sched_setscheduler(pid_t, int, const struct sched_param *);
|
|
|
|
int sched_yield(void);
|
|
|
|
|
|
|
|
#define SCHED_OTHER 0
|
|
|
|
#define SCHED_FIFO 1
|
|
|
|
#define SCHED_RR 2
|
|
|
|
|
overhaul clone syscall wrapping
several things are changed. first, i have removed the old __uniclone
function signature and replaced it with the "standard" linux
__clone/clone signature. this was necessary to expose clone to
applications anyway, and it makes it easier to port __clone to new
archs, since it's now testable independently of pthread_create.
secondly, i have removed all references to the ugly ldt descriptor
structure (i386 only) from the c code and pthread structure. in places
where it is needed, it is now created on the stack just when it's
needed, in assembly code. thus, the i386 __clone function takes the
desired thread pointer as its argument, rather than an ldt descriptor
pointer, just like on all other sane archs. this should not affect
applications since there is really no way an application can use clone
with threads/tls in a way that doesn't horribly conflict with and
clobber the underlying implementation's use. applications are expected
to use clone only for creating actual processes, possibly with new
namespace features and whatnot.
2011-09-18 14:14:37 +00:00
|
|
|
#ifdef _GNU_SOURCE
|
|
|
|
#define CSIGNAL 0x000000ff
|
|
|
|
#define CLONE_VM 0x00000100
|
|
|
|
#define CLONE_FS 0x00000200
|
|
|
|
#define CLONE_FILES 0x00000400
|
|
|
|
#define CLONE_SIGHAND 0x00000800
|
|
|
|
#define CLONE_PTRACE 0x00002000
|
|
|
|
#define CLONE_VFORK 0x00004000
|
|
|
|
#define CLONE_PARENT 0x00008000
|
|
|
|
#define CLONE_THREAD 0x00010000
|
|
|
|
#define CLONE_NEWNS 0x00020000
|
|
|
|
#define CLONE_SYSVSEM 0x00040000
|
|
|
|
#define CLONE_SETTLS 0x00080000
|
|
|
|
#define CLONE_PARENT_SETTID 0x00100000
|
|
|
|
#define CLONE_CHILD_CLEARTID 0x00200000
|
|
|
|
#define CLONE_DETACHED 0x00400000
|
|
|
|
#define CLONE_UNTRACED 0x00800000
|
|
|
|
#define CLONE_CHILD_SETTID 0x01000000
|
|
|
|
#define CLONE_NEWUTS 0x04000000
|
|
|
|
#define CLONE_NEWIPC 0x08000000
|
|
|
|
#define CLONE_NEWUSER 0x10000000
|
|
|
|
#define CLONE_NEWPID 0x20000000
|
|
|
|
#define CLONE_NEWNET 0x40000000
|
|
|
|
#define CLONE_IO 0x80000000
|
|
|
|
int clone (int (*)(void *), void *, int, void *, ...);
|
2012-04-29 23:54:03 +00:00
|
|
|
int unshare(int);
|
2012-09-09 00:22:08 +00:00
|
|
|
int setns(int, int);
|
overhaul clone syscall wrapping
several things are changed. first, i have removed the old __uniclone
function signature and replaced it with the "standard" linux
__clone/clone signature. this was necessary to expose clone to
applications anyway, and it makes it easier to port __clone to new
archs, since it's now testable independently of pthread_create.
secondly, i have removed all references to the ugly ldt descriptor
structure (i386 only) from the c code and pthread structure. in places
where it is needed, it is now created on the stack just when it's
needed, in assembly code. thus, the i386 __clone function takes the
desired thread pointer as its argument, rather than an ldt descriptor
pointer, just like on all other sane archs. this should not affect
applications since there is really no way an application can use clone
with threads/tls in a way that doesn't horribly conflict with and
clobber the underlying implementation's use. applications are expected
to use clone only for creating actual processes, possibly with new
namespace features and whatnot.
2011-09-18 14:14:37 +00:00
|
|
|
#endif
|
|
|
|
|
2011-02-12 05:22:29 +00:00
|
|
|
#ifdef __cplusplus
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
#endif
|