linux-kernel - Re: [RFCv2] perf: proposed perf_event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Nov 2012 20:15:19 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-man@...r.kernel.org, linux-perf-users@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
	Stephane Eranian <eranian@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [RFCv2] perf: proposed perf_event_open() manpage

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/