Skip to content

sched_setscheduler

Implemented in Antinomie 0.7.0 · Syscall list

long sched_setscheduler(pid_t pid, int policy, struct sched_param *param);
Number (x86-64) 144
ABI common
Kernel entry point sys_sched_setscheduler

This is the raw kernel prototype from the pinned Linux 6.12.94 schema, not the libc wrapper.

Sets the scheduling policy and parameters of a process.

Name Type Meaning
pid (arg0) pid_t Process or thread id.
policy (arg1) int Scheduling or memory policy.
param (arg2) struct sched_param * Pointer to a parameter structure.

On success: 0.

In an Antinomie trace the Return column and the ret filter field show the raw kernel return value. On failure that is the negative errno, for example -2 for ENOENT, not the -1 plus errno that the libc wrapper gives. syscall.errno holds the positive errno and syscall.success is false.

Raw return Name Meaning
-22 EINVAL An argument is invalid.
-1 EPERM The operation is not permitted for this process.

sched_setscheduler(2) on man7.org

Coverage mark: Implemented. Every pointer argument has a capture rule in the pinned kernel patch and none of them records a “no decoder”, “address only” or “not observed” gap on any code path. Individual values can still be incomplete on a particular call; see the capture statuses.

Every call is recorded as an Entry record (the six argument words and the pointees copied at entry) and an Exit record (the return value and the pointees copied at exit).

Argument When How Recorded field key Condition
pid (arg0) Entry raw scalar word args.0, args.pid
policy (arg1) Entry raw scalar word args.1, args.policy
param (arg2) Entry the pointer itself, as a raw word args.2, args.raw[2]
↳ pointee Entry structure sched_param (fixed size) arg2.data always
  • Result: ret, syscall.errno, syscall.success, syscall.duration_ns.
  • Argument words: args.pid (arg0), args.policy (arg1), args.param (arg2); args.0 to args.5 by position.
  • Structure sched_param behind param (arg2): args.param.<member> for sched_priority.

See Syscall Trace filter for the full syntax.

For what the capture statuses mean, see Capture statuses. For what is never recorded, see Known gaps.