sched_setparam

Implemented in Antinomie 0.7.0 · Syscall list

Synopsis

long sched_setparam(pid_t pid, struct sched_param *param);

Number (x86-64)	142
ABI	common
Kernel entry point	sys_sched_setparam

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

Description

Sets the scheduling parameters, the priority, of a process without changing its policy.

Arguments

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

Return value

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.

Common errors

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

Man page

sched_setparam(2) on man7.org

Captured by Antinomie

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).

Arguments

Argument	When	How	Recorded field key	Condition
pid (arg0)	Entry	raw scalar word	args.0, args.pid
param (arg1)	Entry	the pointer itself, as a raw word	args.1, args.raw[1]
↳ pointee	Entry	structure sched_param (fixed size)	arg1.data	always

Filter fields

• Result: ret, syscall.errno, syscall.success, syscall.duration_ns.
• Argument words: args.pid (arg0), args.param (arg1); args.0 to args.5 by position.
• Structure sched_param behind param (arg1): 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.