sched_get_priority_max on cris
get static priority range
sys_sched_get_priority_max(int policy)| number | 159 (0x9f) |
|---|---|
| abi | common |
| entry point | sys_sched_get_priority_max |
| since | Linux 3.3 or earlier (3.3 is the first release scanned for cris) |
| man page | sched_get_priority_max(2) |
| source | elixir.bootlin.com |
Registers
| register | value |
|---|---|
r9 | 159, the syscall number |
r10 | int policy |
r10 | the return value |
Then run break 13 to enter the kernel.
This architecture was removed from the Linux kernel in Linux 4.17. The newest release with a syscall table here is Linux 4.16. The other removed architectures live on the historical architectures page.
Same syscall on other architectures
- x64 146
- x86 159
- arm64 125
- arm 159
- riscv64 125
- ia32 159
- x32 1073741970
- loongarch64 125
- ppc64 159
- ppc 159
- s390x 159
- mips64 5143
- mipsn32 6143
- mipso32 4163
- alpha 335
- arc 125
- blackfin 159, removed in 4.17
- csky 125
- frv 159, removed in 4.17
- hexagon 125
- ia64 1165, removed in 6.7
- m32r 159, removed in 4.17
- m68k 159
- metag 125, removed in 4.17
- microblaze 159
- mn10300 159, removed in 4.17
- nds32 125, removed in 5.18
- nios2 125
- openrisc 125
- parisc 159
- score 125, removed in 4.17
- sh 159
- sparc 246
- sparc64 246
- tilegx 125, removed in 4.17
- tilepro 125, removed in 4.17
- xtensa 216
Get this as JSON: https://api.syscall.sh/v2/syscalls/cris/sched_get_priority_max?kernel=all