Changeset View
Changeset View
Standalone View
Standalone View
sys/arm64/linux/linux_locore.asm
Show All 38 Lines | #include <arm64/linux/linux_syscall.h> | ||||
.data | .data | ||||
.globl linux_platform | .globl linux_platform | ||||
linux_platform: | linux_platform: | ||||
.asciz "aarch64" | .asciz "aarch64" | ||||
.text | .text | ||||
nop /* This is what Linux calls a "Mysterious NOP". */ | |||||
ENTRY(__kernel_rt_sigreturn) | ENTRY(__kernel_rt_sigreturn) | ||||
brk #0 /* LINUXTODO: implement __kernel_rt_sigreturn */ | mov x8, #LINUX_SYS_linux_rt_sigreturn | ||||
svc #0 | |||||
dchagin: so does thread cancelation works? according to Linux arch/arm64/kernel/vdso/sugreturn.s… | |||||
Done Inline ActionsTurns out I can fail even at copy/pasting :-D Should be fixed now. trasz: Turns out I can fail even at copy/pasting :-D
Should be fixed now. | |||||
ret | ret | ||||
END(__kernel_rt_sigreturn) | END(__kernel_rt_sigreturn) |
so does thread cancelation works? according to Linux arch/arm64/kernel/vdso/sugreturn.s comments it should not,
as 'gdb, libgcc and libunwind rely on being able to identify the sigreturn instruction sequence to unwind from signal handler'
also see comment about misterious nop instruction. really weird piece of Linux