Skip to contentSkip to conversation

MIPS/MIPS64 syscalls

LTP He Zhe 2 participants 2 messages Aug 19, 2019 – Aug 20, 2019

lore
Share & tools
lore

He Zhe

author
#0 lore raw

Hi All,

There seems not any mips/mips64 syscalls defined. Where can we find them? or do we support them?

ls include/lapi/syscalls/
aarch64.in? hppa.in? ia64.in? powerpc64.in? regen.sh? s390x.in? sparc64.in? strip_syscall.awk arm.in????? i386.in? order??? powerpc.in??? s390.in?? sh.in???? sparc.in??? x86_64.in

Some cases like rt_sigtimedwait01 would fail without the definition.

./testcases/kernel/syscalls/sigwaitinfo/sigwaitinfo01.c
#ifdef TEST_RT_SIGTIMEDWAIT?????????????????????????????????????????????????????
static int my_rt_sigtimedwait(const sigset_t * set, siginfo_t * info,??????????????????????????????????????????????????????????????????????? ????????????????????????????? struct timespec *timeout)????????????????????????? {??????????????????????????????????????????????????????????????????????????????? ????????????????????????????????????????????????????????????????????????????????
??????? /* The last argument is (number_of_signals)/(bits_per_byte), which are 64 and 8, resp. */
??????? return ltp_syscall(__NR_rt_sigtimedwait, set, info, timeout, 8);???????? }???????????????????????????????????????????????????????????????????????????????
#endif

Thanks,
Zhe

#1 lore raw

Hi!

Quoted 2 lines

There seems not any mips/mips64 syscalls defined. Where can we find them? or do we support them?

You need to create these files based on the numbers defined in kernel syscall tables, look at arch/mips/kernel/syscalls/*.tbl, then you need to add newly added architectures into the order file so that the headers are generated correctly.

Also it looks like there are two 32bit ABIs there though not sure if we need to support both in LTP though.

Signature · 2 lines
Cyril Hrubis
[email protected]