arch_prctl(2) | System Calls Manual | arch_prctl(2) |
arch_prctl - set architecture-specific thread state
Standard C library (libc, -lc)
#include <asm/prctl.h> /* Definition of ARCH_* constants */ #include <sys/syscall.h> /* Definition of SYS_* constants */ #include <unistd.h>
int syscall(SYS_arch_prctl, int op, unsigned long addr); int syscall(SYS_arch_prctl, int op, unsigned long *addr);
Note: glibc provides no wrapper for arch_prctl(), necessitating the use of syscall(2).
arch_prctl() sets architecture-specific process or thread state. op selects an operation and passes argument addr to it; addr is interpreted as either an unsigned long for the "set" operations, or as an unsigned long *, for the "get" operations.
Subfunctions for both x86 and x86-64 are:
On success, arch_prctl() returns 0; on error, -1 is returned, and errno is set to indicate the error.
Linux/x86-64.
arch_prctl() is supported only on Linux/x86-64 for 64-bit programs currently.
The 64-bit base changes when a new 32-bit segment selector is loaded.
ARCH_SET_GS is disabled in some kernels.
Context switches for 64-bit segment bases are rather expensive. As an optimization, if a 32-bit TLS base address is used, arch_prctl() may use a real TLS entry as if set_thread_area(2) had been called, instead of manipulating the segment base register directly. Memory in the first 2 GB of address space can be allocated by using mmap(2) with the MAP_32BIT flag.
Because of the aforementioned optimization, using arch_prctl() and set_thread_area(2) in the same thread is dangerous, as they may overwrite each other's TLS entries.
FS may be already used by the threading library. Programs that use ARCH_SET_FS directly are very likely to crash.
mmap(2), modify_ldt(2), prctl(2), set_thread_area(2)
AMD X86-64 Programmer's manual
2024-03-03 | Linux man-pages 6.7 |