mirror of https://github.com/mkerrisk/man-pages
vdso.7: Minor fixes
Reported-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
5e0622bad2
commit
dd6b62ec6e
|
@ -29,7 +29,7 @@ of using any functionality that is available via the vDSO.
|
|||
|
||||
Why does the vDSO exist at all?
|
||||
There are some system calls the kernel provides that
|
||||
user space code ends up using frequently,
|
||||
user-space code ends up using frequently,
|
||||
to the point that such calls can dominate overall performance.
|
||||
This is due both to the frequency of the call as well as the
|
||||
context-switch overhead that results from
|
||||
|
@ -162,7 +162,7 @@ x86/x32 linux-vdso.so.1
|
|||
.in
|
||||
.ft P
|
||||
\}
|
||||
.SH ARCHITECTURE_SPECIFIC NOTES
|
||||
.SH ARCHITECTURE-SPECIFIC NOTES
|
||||
The subsections below provide architecture-specific notes
|
||||
on the vDSO.
|
||||
|
||||
|
@ -172,7 +172,7 @@ Thus, for example,
|
|||
when you run an i386 32-bit ELF binary,
|
||||
you'll get the same vDSO regardless of whether you run it under
|
||||
an i386 32-bit kernel or under an x86_64 64-bit kernel.
|
||||
Thus, the name of the user-space ABI should be used to determine
|
||||
Therefore, the name of the user-space ABI should be used to determine
|
||||
which of the sections below is relevant.
|
||||
.SS ARM functions
|
||||
.\" See linux/arch/arm/kernel/entry-armv.S
|
||||
|
@ -281,7 +281,7 @@ Rather than use the normal ELF auxiliary vector approach,
|
|||
it passes the address of
|
||||
the page to the process via the SR2 register.
|
||||
The permissions on the page are such that merely executing those addresses
|
||||
automatically executes with kernel privileges and not in user-space.
|
||||
automatically executes with kernel privileges and not in user space.
|
||||
This is done to match the way HP-UX works.
|
||||
|
||||
Since it's just a raw page of code, there is no ELF information for doing
|
||||
|
|
Loading…
Reference in New Issue