From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-man@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Stephane Eranian <eranian@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFCv2] perf: proposed perf_event_open() manpage
Date: Tue, 6 Nov 2012 20:15:19 -0300 [thread overview]
Message-ID: <20121106231519.GH3430@ghostprotocols.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1211061748120.30004@vincent-weaver-1.um.maine.edu>
Em Tue, Nov 06, 2012 at 05:53:27PM -0500, Vince Weaver escreveu:
> .TP
> .IR "mmap"
> The
> .I mmap
> bit enables recording of extra information to a
> mmap'd ring-buffer.
> This is
> described below in subsection MMAP Layout.
Enables the recording of exec mmap events, its counterpart, for data
maps is...
> .IR "mmap_data" " (Since Linux 2.6.36)"
> Include mmap events in the ring_buffer.
That will include mmap events for data maps.
> .TP
> .IR "sample_id_all" " (Since Linux 2.6.38)"
> If set, then all sample ID info (TID, TIME, ID, CPU, STREAM_ID)
> will be provided.
No, it will obey sample_type for non SAMPLE PERF_RECORD_ events,
so if you want timestamps in all events so that you can detect
reordering, use it a sample_type with PERF_SAMPLE_TIME and
sample_id_all.
I'll read it again tomorrow, thanks for writing it!
- Arnaldo
next prev parent reply other threads:[~2012-11-06 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 22:53 [RFCv2] perf: proposed perf_event_open() manpage Vince Weaver
2012-11-06 23:15 ` Arnaldo Carvalho de Melo [this message]
2012-11-07 21:55 ` Vince Weaver
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=20121106231519.GH3430@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulus@samba.org \
--cc=vincent.weaver@maine.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.