Section (3) getauxval
getauxval — retrieve a value from the auxiliary vector
||unsigned long type
retrieves values from the auxiliary vector, a mechanism that
the kernel_zsingle_quotesz_s ELF binary loader uses to pass certain
information to user space when a program is executed.
Each entry in the auxiliary vector consists of a pair of
values: a type that identifies what this entry represents,
and a value for that type. Given the argument
getauxval() returns the corresponding
The value returned for each
type is given in the following
list. Not all
values are present on all architectures.
The base address of the program interpreter (usually, the dynamic linker).
A pointer to a string identifying the real platform; may differ from
The frequency with which times(2) counts. This value can also be obtained via
The data cache block size.
The effective group ID of the thread.
The entry address of the executable.
The effective user ID of the thread.
File descriptor of program.
A pointer to a string containing the pathname used to execute the program.
Used FPU control word (SuperH architecture only). This gives some information about the FPU initialization performed by the kernel.
The real group ID of the thread.
An architecture and ABI dependent bit-mask whose settings indicate detailed processor capabilities. The contents of the bit mask are hardware dependent (for example, see the kernel source file
arch/x86/include/asm/cpufeature.hfor details relating to the Intel x86 architecture; the value returned is the first 32-bit word of the array described there). A human-readable version of the same information is available via
AT_HWCAP2(since glibc 2.18)
Further machine-dependent hints about processor capabilities.
The instruction cache block size.
Geometry of the L1 data cache, encoded with the cache line size in bytes in the bottom 16 bits and the cache associativity in the next 16 bits. The associativity is such that if N is the 16-bit value, the cache is N-way set associative.
The L1 data cache size.
Geometry of the L1 instruction cache, encoded as for
The L1 instruction cache size.
Geometry of the L2 cache, encoded as for
The L2 cache size.
Geometry of the L3 cache, encoded as for
The L3 cache size.
The system page size (the same value returned by
The address of the program headers of the executable.
The size of program header entry.
The number of program headers.
A pointer to a string that identifies the hardware platform that the program is running on. The dynamic linker uses this in the interpretation of
The address of sixteen bytes containing a random value.
Has a nonzero value if this executable should be treated securely. Most commonly, a nonzero value indicates that the process is executing a set-user-ID or set-group-ID binary (so that its real and effective UIDs or GIDs differ from one another), or that it gained capabilities by executing a binary file that has capabilities (see capabilities(7)). Alternatively, a nonzero value may be triggered by a Linux Security Module. When this value is nonzero, the dynamic linker disables the use of certain environment variables (see ld-linux.so(8)) and glibc changes other aspects of its behavior. (See also secure_getenv(3).)
The entry point to the system call function in the vDSO. Not present/needed on all architectures (e.g., absent on x86-64).
The address of a page containing the virtual Dynamic Shared Object (vDSO) that the kernel creates in order to provide fast implementations of certain system calls.
The unified cache block size.
The real user ID of the thread.
returns the value corresponding to
type is not found, 0 is
- ENOENT (since glibc 2.19)
No entry corresponding to
typecould be found in the auxiliary vector.
For an explanation of the terms used in this section, see attributes(7).
The primary consumer of the information in the auxiliary vector is the dynamic linker, ld-linux.so(8). The auxiliary vector is a convenient and efficient shortcut that allows the kernel to communicate a certain set of standard information that the dynamic linker usually or always needs. In some cases, the same information could be obtained by system calls, but using the auxiliary vector is cheaper.
The auxiliary vector resides just above the argument list
and environment in the process address space. The auxiliary
vector supplied to a program can be viewed by setting the
variable when running a program:
$ LD_SHOW_AUXV=1 sleep 1
The auxiliary vector of any process can (subject to file
permissions) be obtained via
/proc/[pid]/auxv; see proc(5) for more
Before the addition of the ENOENT error in glibc 2.19, there was no
way to unambiguously distinguish the case where
type could not be found from
the case where the value corresponding to
type was zero.
This page is part of release 5.04 of the Linux
man-pages project. A
description of the project, information about reporting bugs,
and the latest version of this page, can be found at
Copyright 2012 Michael Kerrisk <mtk.manpagesgmail.com>
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this
manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
Since the Linux kernel and libraries are constantly changing, this
manual page may be incorrect or out-of-date. The author(s) assume no
responsibility for errors or omissions, or for damages resulting from
the use of the information contained herein. The author(s) may not
have taken the same level of care in the production of this manual,
which is licensed free of charge, as they might when working
Formatted or processed versions of this manual, if unaccompanied by
the source, must acknowledge the copyright and authors of this work.
See also https://lwn.net/Articles/519085/