Searched refs:schedulers (Results 1 – 11 of 11) sorted by relevance
12 tcp->auxstr = xlookup(schedulers, tcp->u_rval); in SYS_FUNC()24 printxval(schedulers, tcp->u_arg[1], "SCHED_???"); in SYS_FUNC()62 printxval(schedulers, tcp->u_arg[0], "SCHED_???"); in SYS_FUNC()
3 static const struct xlat schedulers[] = { variable
1 ….in xlat/rename_flags.in xlat/resource_flags.in xlat/resources.in xlat/schedulers.in xlat/scmvals.…2 …ypes.h xlat/rename_flags.h xlat/resource_flags.h xlat/resources.h xlat/schedulers.h xlat/scmvals.h…287 $(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
211 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
321 An important consideration when analyzing block IO schedulers is to
16 // required until SD and PostRA schedulers are replaced by MachineScheduler.
1297 option. Registering instruction schedulers is similar except use the