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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
