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:	Mon, 4 May 2015 22:02:16 +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 02/24] perf tools: Add AUX area tracing index

On Thu, Apr 30, 2015 at 05:37:25PM +0300, Adrian Hunter wrote:
> Add an index of AUX area tracing events within
> a perf.data file.
> 
> perf record uses a special user event
> PERF_RECORD_FINISHED_ROUND to enable sorting of
> events in chunks instead of having to sort all
> events altogether.
> 
> AUX area tracing events contain data that can
> span back to the very beginning of the recording
> period. i.e. they do not obey the rules of
> PERF_RECORD_FINISHED_ROUND.
> 
> By adding an index, AUX area tracing events
> can be found in advance and the
> PERF_RECORD_FINISHED_ROUND approach works as
> usual.
> 
> The index is recorded with the auxtrace feature
> in the perf.data file.  A session reads the index
> but does not process it.  An AUX area
> decoder can queue all the AUX area data
> in advance using auxtrace_queues__process_index()
> or otherwise process the index in some custom
> manner.
> 
> 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ