From 2b23ecbdea2456baac995d68f4afffa069927861 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Thu, 17 Apr 2014 09:44:58 +0200 Subject: [PATCH] perf_event_open.2: Explain the EACCES "monitoring all processes" case more precisely Signed-off-by: Michael Kerrisk --- man2/perf_event_open.2 | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 494e7cbcf..d2d6e5c5a 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -24,7 +24,7 @@ .\" This document is based on the perf_event.h header file, the .\" tools/perf/design.txt file, and a lot of bitter experience. .\" -.TH PERF_EVENT_OPEN 2 2014-04-10 "Linux" "Linux Programmer's Manual" +.TH PERF_EVENT_OPEN 2 2014-04-17 "Linux" "Linux Programmer's Manual" .SH NAME perf_event_open \- set up performance monitoring .SH SYNOPSIS @@ -2404,8 +2404,9 @@ permissions (or a more permissive perf_event paranoid setting). Some common cases where an unprivileged process may encounter this error: attaching to a process owned by a different user; -monitoring all processes (including those not belonging to the user) -on a given CPU; +monitoring all processes on a given CPU (i.e., specifying the +.I pid +argument as \-1); and not setting .I exclude_kernel when the paranoid setting requires it.