linux-kernel - Re: [PATCH V4 06/24] perf tools: Add support for PERF_RECORD

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 4 May 2015 22:09:48 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Namhyung Kim <namhyung@...il.com>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH V4 06/24] perf tools: Add support for PERF_RECORD_AUX

On Thu, Apr 30, 2015 at 05:37:29PM +0300, Adrian Hunter wrote:
> Add support for the PERF_RECORD_AUX event type.
> 
> PERF_RECORD_AUX is a new kernel event that records
> when new data lands in the AUX buffer. Currently
> it is assumed that AUX data follows the same ring
> buffer conventions used by the perf events buffer,
> and consequently the AUX event is not processed
> during recording.
> 
> It is processed during session processing so that
> the information in the 'flags' member is made
> available.
> 
> The format of PERF_RECORD_AUX is outlined in the
> linux/perf_events.h header file. The 'flags' are
> also enumerated.
> 
> Intel PT and Intel BTS use the flag named
> PERF_AUX_FLAG_TRUNCATED to determine if data has
> been lost because the buffer became full as
> perf was not able to empty it fast enough.
> 
> Signed-off-by: Adrian Hunter <adrian.hunter@...el.com>

Acked-by: Jiri Olsa <jolsa@...nel.org>

thanks,
jirka
--
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/