perf_event_open.2: tfix

Reported-by: David Prévot <taffit@debian.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2013-02-25 06:24:53 +01:00
parent 7ede2f66dc
commit ad73a2ccc9
1 changed files with 4 additions and 4 deletions

View File

@ -613,7 +613,7 @@ timer tick.
The various bits in this field specify which values to include
in the sample.
They will be recorded in a ring-buffer,
which is available to user-space using
which is available to user space using
.BR mmap (2).
The order in which the values are saved in the
sample are documented in the MMAP Layout subsection below;
@ -753,7 +753,7 @@ disrupt other hardware counters.
.TP
.IR "exclude_user"
If this bit is set, the count excludes events that happen in user-space.
If this bit is set, the count excludes events that happen in user space.
.TP
.IR "exclude_kernel"
@ -1300,7 +1300,7 @@ The value needs to be manually wrapped by the size of the mmap buffer
before accessing the samples.
On SMP-capable platforms, after reading the data_head value,
user-space should issue an rmb().
user space should issue an rmb().
.TP
.I data_tail;
@ -1362,7 +1362,7 @@ selected as shown.
The MMAP events record the
.B PROT_EXEC
mappings so that we can correlate
user space IPs to code.
user-space IPs to code.
They have the following structure:
.in +4n