aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2016-10-29 12:15:22 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2016-10-29 13:31:50 +0200
commitb51901524846875d86c7cea9acc783c6f152cc72 (patch)
tree35f702b34fac81763194fb5f87bdd4ecf2cdd8fb
parent3af37891fd20b5e5eedcbc92a12b03e0d2635a36 (diff)
downloadman-pages-b51901524846875d86c7cea9acc783c6f152cc72.tar.gz
perf_event_open.2: srcfix: FIXME tidy-up
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/perf_event_open.25
1 files changed, 3 insertions, 2 deletions
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 8d985b398a..6d77d970d9 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -3211,10 +3211,11 @@ This means to see if a given set of events works you have to
start, then read before you know for sure you
can get valid measurements.
-Prior to Linux 2.6.34, event constraints were not enforced by the kernel.
+Prior to Linux 2.6.34,
+.\" FIXME . cannot find a kernel commit for this one
+event constraints were not enforced by the kernel.
In that case, some events would silently return "0" if the kernel
scheduled them in an improper counter slot.
-.\" FIXME: cannot find a kernel commit for this one
Prior to Linux 2.6.34, there was a bug when multiplexing where the
wrong results could be returned.