Searched refs:SCHED_DEADLINE (Results 1 - 10 of 10) sorted by relevance

/linux-master/tools/perf/trace/beauty/
H A Dsched_policy.c10 #ifndef SCHED_DEADLINE
11 #define SCHED_DEADLINE 6 macro
30 if (policy <= SCHED_DEADLINE)
/linux-master/include/linux/sched/
H A Drt.h27 if (policy == SCHED_DEADLINE)
/linux-master/include/uapi/linux/
H A Dsched.h120 #define SCHED_DEADLINE 6 macro
/linux-master/tools/include/uapi/linux/
H A Dsched.h120 #define SCHED_DEADLINE 6 macro
/linux-master/tools/tracing/rtla/src/
H A Dutils.c212 * This is a set of helper functions to use SCHED_DEADLINE.
234 #define SCHED_DEADLINE 6 macro
403 * SCHED_DEADLINE:
434 sched_param->sched_policy = SCHED_DEADLINE;
/linux-master/drivers/cpufreq/
H A Dcppc_cpufreq.c220 .sched_policy = SCHED_DEADLINE,
254 pr_warn("%s: failed to set SCHED_DEADLINE: %d\n", __func__,
/linux-master/kernel/sched/
H A Dcpufreq_schedutil.c649 .sched_policy = SCHED_DEADLINE,
681 pr_warn("%s: failed to set SCHED_DEADLINE\n", __func__);
H A Dsched.h161 * Single value that decides SCHED_DEADLINE internal math precision.
188 return policy == SCHED_DEADLINE;
231 * It is used to make schedutil kworker(s) higher priority than SCHED_DEADLINE
319 * SCHED_DEADLINE supports servers (nested scheduling) with the following
H A Dcore.c7295 * SCHED_DEADLINE, SCHED_FIFO or SCHED_RR:
7670 * Can't set/change SCHED_DEADLINE policy at all for now
7767 * SCHED_DEADLINE bandwidth accounting relies on stable cpusets
7833 * the entire root_domain to become SCHED_DEADLINE. We
7855 * If setscheduling to SCHED_DEADLINE (or changing the parameters
7856 * of a SCHED_DEADLINE task) we need to check if enough bandwidth
9066 case SCHED_DEADLINE:
9093 case SCHED_DEADLINE:
/linux-master/kernel/trace/
H A Dtrace_selftest.c1158 .sched_policy = SCHED_DEADLINE,

Completed in 202 milliseconds