Searched refs:schedulers (Results 1 – 11 of 11) sorted by relevance
42 tcp->auxstr = xlookup(schedulers, tcp->u_rval); in SYS_FUNC()52 printxval(schedulers, tcp->u_arg[1], "SCHED_???"); in SYS_FUNC()78 printxval(schedulers, tcp->u_arg[0], "SCHED_???"); in SYS_FUNC()116 printxval(schedulers, attr.sched_policy, "SCHED_???"); in print_sched_attr()
5 # error static const struct xlat schedulers in mpers mode10 const struct xlat schedulers[] = { variable
1 …s.in xlat/resource_flags.in xlat/resources.in xlat/sched_flags.in xlat/schedulers.in xlat/scmvals.…2 …flags.h xlat/resource_flags.h xlat/resources.h xlat/sched_flags.h xlat/schedulers.h xlat/scmvals.h…321 $(top_srcdir)/xlat/schedulers.h: $(top_srcdir)/xlat/schedulers.in $(top_srcdir)/xlat/gen.sh
6 ; The top-down schedulers are excluded here because they don't yet support
155 Instruction schedulers available (before register allocation):
74 // as two micro-ops when dispatched by the schedulers.
365 of the Linux IO subsystem and schedulers. He got tired of writing
16 // required until SD and PostRA schedulers are replaced by MachineScheduler.
321 An important consideration when analyzing block IO schedulers is to
1293 option. Registering instruction schedulers is similar except use the