From 8a94e783a96d28dcdbd868568eb0960cba114583 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Wed, 31 Jul 2013 08:45:42 +0200 Subject: [PATCH] Removed trailing white space at end of lines --- man2/linkat.2 | 2 +- man2/perf_event_open.2 | 24 ++++++++++++------------ man8/ld.so.8 | 4 ++-- 3 files changed, 15 insertions(+), 15 deletions(-) diff --git a/man2/linkat.2 b/man2/linkat.2 index c7bb3ecb1..701d3411b 100644 --- a/man2/linkat.2 +++ b/man2/linkat.2 @@ -103,7 +103,7 @@ The following values can be biwise ORed in If .I oldpath is an empty string, create a link to the file referenced by -.IR olddirfd +.IR olddirfd (which may have been obtained using the .BR open (2) .B O_PATH diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 19061c611..c7f577dbd 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -965,7 +965,7 @@ is a further extension of the field. .TP .IR "branch_sample_type" " (Since Linux 3.4)" -If +If .B PERF_SAMPLE_BRANCH_STACK is enabled, then this specifies what branches to include in the branch record. @@ -973,7 +973,7 @@ If the user does not set privilege level explicitly, the kernel will use the event's privilege level. Event and branch privilege levels do not have to match. The value is formed by ORing together zero or more of the following values, -although +although .B PERF_SAMPLE_BRANCH_ANY covers all branch types. .RS @@ -1577,10 +1577,10 @@ the branch target was predicted. The entries are from most to least recent, so the first entry has the most recent branch. -Support for -.I mispred -and -.I predicted +Support for +.I mispred +and +.I predicted is optional; if not supported, both values will be 0. @@ -1975,7 +1975,7 @@ This contains an integer that can be used in the field of perf_event_attr to indicate you wish to use this PMU. .TP .IR /sys/bus/event_source/devices/*/rdpmc " (Since Linux 3.4)" -If this file is 1, then direct user-space access to the +If this file is 1, then direct user-space access to the performance counter registers is allowed via the rdpmc instruction. This can be disabled by echoing 0 to the file. .TP @@ -1988,7 +1988,7 @@ fields in the perf_event_attr struct. The content of each file is the name of the config field, followed by a colon, followed by a series of integer bit ranges separated by commas. -For example, the file +For example, the file .I event may contain the value .I config1:1,6-10,44 @@ -2005,8 +2005,8 @@ These are not necessarily complete lists of all events supported by 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). +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 field with a value of 1. An example entry may look like this: @@ -2017,7 +2017,7 @@ 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 +The 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 @@ -2104,7 +2104,7 @@ Linux 2.6.36 and Linux 3.0 that ignores the was chosen if the union has a non-zero value in it. -From Linux 2.6.31 to Linux 3.4, the +From Linux 2.6.31 to Linux 3.4, the .B PERF_IOC_FLAG_GROUP ioctl argument was broken and would repeatedly operate on the event specified rather than iterating across diff --git a/man8/ld.so.8 b/man8/ld.so.8 index d807bd4f5..71a7ed37d 100644 --- a/man8/ld.so.8 +++ b/man8/ld.so.8 @@ -91,7 +91,7 @@ linker option, this step is skipped. understands certain strings in an rpath specification (DT_RPATH or DT_RUNPATH); those strings are substituted as follows .TP .IR $ORIGIN " (or equivalently " ${ORIGIN} ) -This expands to +This expands to the directory containing the application executable. Thus, an application located in .I somedir/app @@ -231,7 +231,7 @@ different minimum kernel ABI version requirements, can be used to select the version of the library that is used (dependent on the directory search order). Historically, the most common use of the -.BR LD_ASSUME_KERNEL +.BR LD_ASSUME_KERNEL feature was to manually select the older LinuxThreads POSIX threads implementation on systems that provided both LinuxThreads and NPTL