diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-10-14 12:54:42 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-10-14 12:54:42 +0200 |
| commit | 5d73bc3fe440dd56ff00103d894e484caa893d1a (patch) | |
| tree | 35ded3dfe22af5d4d1fccb3a5d2ca694aa61114f | |
| parent | dc9ec146ab340c1b564b02ca80ce5a56f6d91520 (diff) | |
| download | man-pages-5d73bc3fe440dd56ff00103d894e484caa893d1a.tar.gz | |
perf_event_open.2: wfix
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
| -rw-r--r-- | man2/perf_event_open.2 | 28 |
1 files changed, 13 insertions, 15 deletions
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index fab3c7f9c0..afdee49eda 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -789,7 +789,7 @@ the register values will return kernel register state if the overflow happened while kernel code is running. If the CPU supports hardware sampling of -register state (i.e. PEBS on Intel x86) and +register state (i.e.,, PEBS on Intel x86) and .I precise_ip is set higher than zero then the register values returned are those captured by @@ -982,7 +982,7 @@ better and allows more accurate reporting of which events correspond to which instructions, but hardware is often limited with how small this can be. -The values of this are the following: +The possible values of this field are the following: .RS .IP 0 3 .B SAMPLE_IP @@ -996,13 +996,13 @@ requested to have 0 skid. .IP 3 .B SAMPLE_IP must have 0 skid. -See also +See also the description of .BR PERF_RECORD_MISC_EXACT_IP . .RE .TP .IR "mmap_data" " (since Linux 2.6.36)" .\" commit 3af9e859281bda7eb7c20b51879cf43aa788ac2e -The counterpart of the +Ths the counterpart of the .I mmap field. This enables generation of @@ -1047,10 +1047,10 @@ struct sample_id { .IR "exclude_host" " (since Linux 3.2)" .\" commit a240f76165e6255384d4bdb8139895fac7988799 When conducting measurements that include processes running -VM instances (i.e. have executed a -.I KVM_RUN -.BR ioctl (2) -) only measure events happening inside a guest instance. +VM instances (i.e., have executed a +.B KVM_RUN +.BR ioctl (2)), +only measure events happening inside a guest instance. This is only meaningful outside the guests; this setting does not change counts gathered inside of a guest. Currently, this functionality is x86 only. @@ -1058,10 +1058,10 @@ Currently, this functionality is x86 only. .IR "exclude_guest" " (since Linux 3.2)" .\" commit a240f76165e6255384d4bdb8139895fac7988799 When conducting measurements that include processes running -VM instances (i.e. have executed a -.I KVM_RUN -.BR ioctl (2) -) do not measure events happening inside guest instances. +VM instances (i.e., have executed a +.B KVM_RUN +.BR ioctl (2)), +do not measure events happening inside guest instances. This is only meaningful outside the guests; this setting does not change counts gathered inside of a guest. Currently, this functionality is x86 only. @@ -1171,8 +1171,7 @@ is not allowed. .TP .IR "bp_addr" " (since Linux 2.6.33)" .\" commit 24f1e32c60c45c89a997c73395b69c8af6f0a84e -.I bp_addr -address of the breakpoint. +This is the address of the breakpoint. For execution breakpoints this is the memory address of the instruction of interest; for read and write breakpoints it is the memory address of the memory location of interest. @@ -1202,7 +1201,6 @@ For an execution breakpoint, set this to .TP .IR "config2" " (since Linux 2.6.39)" .\" commit a7e3ed1e470116c9d12c2f778431a481a6be8ab6 - .I config2 is a further extension of the .I config1 |