From: Daniel Colascione <dancol@google.com>
To: Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>, Tim Murray <timmurray@google.com>
Subject: [PATCH] Mention EINTR for perf_event_open
Date: Wed, 8 Jan 2020 15:57:18 -0800 [thread overview]
Message-ID: <CAKOZuesChdRSgY+W90kPJkg8UQzqt66ngsg8sX1VCLCvVdfDUQ@mail.gmail.com> (raw)
Somewhat surprisingly, perf_event_open can fail with EINTR when trying
to enable perf reporting for a uprobe that's already been configured
for use with ftrace. Mention this error in the man page.
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 25876c36c..b9128f542 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -3228,6 +3228,10 @@ values are out of range or set reserved bits;
the generic event selected is not supported; or
there is not enough room to add the selected event.
.TP
+.B EINTR
+Returned when trying to mix perf and ftrace handling
+for a uprobe.
+.TP
.B EMFILE
Each opened event uses one file descriptor.
If a large number of events are opened,
next reply other threads:[~2020-01-08 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 23:57 Daniel Colascione [this message]
2020-01-21 19:49 ` [PATCH] Mention EINTR for perf_event_open Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKOZuesChdRSgY+W90kPJkg8UQzqt66ngsg8sX1VCLCvVdfDUQ@mail.gmail.com \
--to=dancol@google.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=timmurray@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).