sched_get_priority_min on mn10300
get static priority range
sys_sched_get_priority_min(int policy)| number | 160 (0xa0) |
|---|---|
| abi | common |
| entry point | sys_sched_get_priority_min |
| since | Linux 3.3 or earlier (3.3 is the first release scanned for mn10300) |
| man page | sched_get_priority_min(2) |
| source | elixir.bootlin.com |
Registers
| register | value |
|---|---|
d0 | 160, the syscall number |
a0 | int policy |
d0 | the return value |
Then run syscall 0 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 147
- x86 160
- arm64 126
- arm 160
- riscv64 126
- ia32 160
- x32 1073741971
- loongarch64 126
- ppc64 160
- ppc 160
- s390x 160
- mips64 5144
- mipsn32 6144
- mipso32 4164
- alpha 336
- arc 126
- blackfin 160, removed in 4.17
- cris 160, removed in 4.17
- csky 126
- frv 160, removed in 4.17
- hexagon 126
- ia64 1166, removed in 6.7
- m32r 160, removed in 4.17
- m68k 160
- metag 126, removed in 4.17
- microblaze 160
- nds32 126, removed in 5.18
- nios2 126
- openrisc 126
- parisc 160
- score 126, removed in 4.17
- sh 160
- sparc 247
- sparc64 247
- tilegx 126, removed in 4.17
- tilepro 126, removed in 4.17
- xtensa 217
Get this as JSON: https://api.syscall.sh/v2/syscalls/mn10300/sched_get_priority_min?kernel=all