From: Vince Weaver <vincent.weaver@maine.edu>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
Kan Liang <kan.liang@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Stephane Eranian <eranian@gmail.com>
Subject: [patch] perf_event_open.2: PERF_RECORD_LOST_SAMPLES record type
Date: Sat, 15 Oct 2016 22:02:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1610152201370.4137@macbook-air> (raw)
Linux 4.2 added a new record type: PERF_RECORD_LOST_SAMPLES
It is generated when hardware samples (currently only Intel PEBS)
are lost.
Signed-off-by: Vince Weaver <vincent.weaver@maine.edu>
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 9f33122..a47df2d 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -2551,6 +2551,25 @@ process ID of the thread starting an instruction trace.
.I tid
thread ID of the thread starting an instruction trace.
.RE
+.TP
+.BR PERF_RECORD_LOST_SAMPLES " (since Linux 4.2)"
+\" f38b0dbb491a6987e198aa6b428db8692a6480f8
+When using hardware sampling (such as Intel PEBS) this record
+indicates some number of samples may have been lost.
+
+.in +4n
+.nf
+struct {
+ struct perf_event_header header;
+ u64 lost;
+ struct sample_id sample_id;
+};
+.fi
+.RS
+.TP
+.I lost
+the number of potentially lost samples.
+.RE
.RE
.SS Overflow handling
Events can be set to notify when a threshold is crossed,
next reply other threads:[~2016-10-16 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 2:02 Vince Weaver [this message]
2016-10-17 6:46 ` 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=alpine.DEB.2.20.1610152201370.4137@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=eranian@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®