[PATCH] perf_event_open.2: ffix

[PATCH] perf_event_open.2: ffix

[David Prévot]

---
 man2/perf_event_open.2 |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 6d42c41..260e772 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -797,11 +797,11 @@ If set, don't count when the CPU is idle.
 The
 .I mmap
 bit enables generation of
-.I PERF_RECORD_MMAP
+.B PERF_RECORD_MMAP
 samples for every
 .BR mmap (2)
 call that has
-.I PROT_EXEC
+.B PROT_EXEC
 set.
 This allows tools to notice new executable code being mapped into
 a program (dynamic shared libraries for example)
@@ -811,9 +811,9 @@ so that addresses can be mapped back to the original code.
 The
 .I comm
 bit enables tracking of process command name as modified by the
-.IR exec (2)
+.BR exec (2)
 and
-.IR prctl (PR_SET_NAME)
+.BR prctl (PR_SET_NAME)
 system calls.
 Unfortunately for tools,
 there is no way to distinguish one system call versus the other.
@@ -886,11 +886,11 @@ The counterpart of the
 .I mmap
 field.
 This enables generation of
-.I PERF_RECORD_MMAP
+.B PERF_RECORD_MMAP
 samples for
 .BR mmap (2)
 calls that do not have
-.I PROT_EXEC
+.B PROT_EXEC
 set (for example data and SysV shared memory).
 .TP
 .IR "sample_id_all" " (Since Linux 2.6.38)"
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] perf_event_open.2: ffix

[Michael Kerrisk (man-pages)]

Thanks, David. Applied.

Cheers,

Michael



On 12/16/13 11:16, David Prévot wrote:
> ---
>  man2/perf_event_open.2 |   12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index 6d42c41..260e772 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -797,11 +797,11 @@ If set, don't count when the CPU is idle.
>  The
>  .I mmap
>  bit enables generation of
> -.I PERF_RECORD_MMAP
> +.B PERF_RECORD_MMAP
>  samples for every
>  .BR mmap (2)
>  call that has
> -.I PROT_EXEC
> +.B PROT_EXEC
>  set.
>  This allows tools to notice new executable code being mapped into
>  a program (dynamic shared libraries for example)
> @@ -811,9 +811,9 @@ so that addresses can be mapped back to the original code.
>  The
>  .I comm
>  bit enables tracking of process command name as modified by the
> -.IR exec (2)
> +.BR exec (2)
>  and
> -.IR prctl (PR_SET_NAME)
> +.BR prctl (PR_SET_NAME)
>  system calls.
>  Unfortunately for tools,
>  there is no way to distinguish one system call versus the other.
> @@ -886,11 +886,11 @@ The counterpart of the
>  .I mmap
>  field.
>  This enables generation of
> -.I PERF_RECORD_MMAP
> +.B PERF_RECORD_MMAP
>  samples for
>  .BR mmap (2)
>  calls that do not have
> -.I PROT_EXEC
> +.B PROT_EXEC
>  set (for example data and SysV shared memory).
>  .TP
>  .IR "sample_id_all" " (Since Linux 2.6.38)"
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] perf_event_open.2: ffix

[David Prévot]

---
 man2/perf_event_open.2 | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index c7f577d..f96df8c 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -164,7 +164,7 @@ This flag re-routes the output from an event to the group leader.
 This flag activates per-container system-wide monitoring.
 A container
 is an abstraction that isolates a set of resources for finer grain
-control (CPUs, memory, etc...).
+control (CPUs, memory, etc.).
 In this mode, the event is measured
 only if the thread running on the monitored CPU belongs to the designated
 container (cgroup).
@@ -2010,15 +2010,17 @@ Each entry has an optional value (either hex or decimal).
 If no value is specified than it is assumed to be a single-bit
 field with a value of 1.
 An example entry may look like this:
-.I event=0x2,inv,ldlat=3
+.IR event=0x2,inv,ldlat=3 .
 .TP
 .I /sys/bus/event_source/devices/*/uevent
 This file is the standard kernel device interface
 for injecting hotplug events.
 .TP
 .IR /sys/bus/event_source/devices/*/cpumask " (Since Linux 3.7)"
-The cpumask file contains a comma-separated list of integers that
-indicate a representative cpu number for each socket (package)
+The
+.I cpumask
+file contains a comma-separated list of integers that
+indicate a representative CPU number for each socket (package)
 on the motherboard.
 This is needed when setting up uncore or northbridge events, as
 those PMUs present socket-wide events.
-- 
1.8.4.rc3

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] perf_event_open.2: ffix

[Michael Kerrisk (man-pages)]

Thanks, David. Applied.

Cheers,

Michael


On 09/03/13 05:16, David Prévot wrote:
> ---
>  man2/perf_event_open.2 | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
> diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
> index c7f577d..f96df8c 100644
> --- a/man2/perf_event_open.2
> +++ b/man2/perf_event_open.2
> @@ -164,7 +164,7 @@ This flag re-routes the output from an event to the group leader.
>  This flag activates per-container system-wide monitoring.
>  A container
>  is an abstraction that isolates a set of resources for finer grain
> -control (CPUs, memory, etc...).
> +control (CPUs, memory, etc.).
>  In this mode, the event is measured
>  only if the thread running on the monitored CPU belongs to the designated
>  container (cgroup).
> @@ -2010,15 +2010,17 @@ Each entry has an optional value (either hex or decimal).
>  If no value is specified than it is assumed to be a single-bit
>  field with a value of 1.
>  An example entry may look like this:
> -.I event=0x2,inv,ldlat=3
> +.IR event=0x2,inv,ldlat=3 .
>  .TP
>  .I /sys/bus/event_source/devices/*/uevent
>  This file is the standard kernel device interface
>  for injecting hotplug events.
>  .TP
>  .IR /sys/bus/event_source/devices/*/cpumask " (Since Linux 3.7)"
> -The cpumask file contains a comma-separated list of integers that
> -indicate a representative cpu number for each socket (package)
> +The
> +.I cpumask
> +file contains a comma-separated list of integers that
> +indicate a representative CPU number for each socket (package)
>  on the motherboard.
>  This is needed when setting up uncore or northbridge events, as
>  those PMUs present socket-wide events.
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html