LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

perf_event_open.2: wfix + grfix 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-03-26 05:40:00 +01:00
parent f1ad56a654
commit 37bee118ad
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
man2/perf_event_open.2
View File

@ -583,7 +583,7 @@ field controls what data is recorded on each interrupt.
.I sample_freq
can be used if you wish to use frequency rather than period.
In this case you set the
In this case, you set the
.I freq
flag.
The kernel will adjust the sampling period
@ -933,7 +933,7 @@ is selected.
If
.B PERF_SAMPLE_IDENTIFIER
is specified than an additional ID value is included
is specified, then an additional ID value is included
as the last value to ease parsing the record stream.
This may lead to the
.I id
@ -1176,10 +1176,10 @@ was specified.
.IR time_enabled ", " time_running
Total time the event was enabled and running.
Normally these are the same.
If more events are started
than available counter slots on the PMU, then multiplexing
If more events are started,
then available counter slots on the PMU, then multiplexing
happens and events run only part of the time.
In that case the
In that case, the
.I time_enabled
and
.I time running
@ -1296,7 +1296,7 @@ fields instead.
.TP
.IR cap_bit0_is_deprecated " (since Linux 3.12)"
If set this bit indicates that the kernel supports
If set, this bit indicates that the kernel supports
the properly separated
.I cap_user_time
and
@ -1413,7 +1413,7 @@ enabled and possible running (if idx), improving the scaling:
If
.I cap_usr_time_zero
is set then the hardware clock (the TSC timestamp counter on x86)
is set, then the hardware clock (the TSC timestamp counter on x86)
can be calculated from the
.IR time_zero ", " time_mult ", and " time_shift " values:"
.nf
@ -2033,7 +2033,7 @@ OS fault handler
.I transaction
If the
.B PERF_SAMPLE_TRANSACTION
flag is set then a 64-bit field is recorded describing
flag is set, then a 64-bit field is recorded describing
the sources of any transactional memory aborts.
The field is a bitwise combination of the following values:
@ -2321,7 +2321,7 @@ a PMU, but usually a subset of events deemed useful or interesting.
The content of each file is a list of attribute names
separated by commas.
Each entry has an optional value (either hex or decimal).
If no value is specified than it is assumed to be a single-bit
If no value is specified, then it is assumed to be a single-bit
field with a value of 1.
An example entry may look like this:
.IR event=0x2,inv,ldlat=3 .