linux-kernel - Re: [PATCH 4/6] perf script: add call path id to exported sample in db export

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]

Message-ID: <20160506122339.GZ11069@kernel.org>
Date:	Fri, 6 May 2016 09:23:39 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	Chris Phlipot <cphlipot0@...il.com>, jolsa@...nel.org,
	peterz@...radead.org, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/6] perf script: add call path id to exported sample in
 db export

Em Fri, May 06, 2016 at 02:28:05PM +0300, Adrian Hunter escreveu:
> On 28/04/16 11:19, Chris Phlipot wrote:
> > The exported sample now contains a reference to the call_path_id that
> > represents its callchain.
> > 
> > While callchains themselves are nice to have, being able to associate
> > them with samples makes them much more useful, and can allow for such
> > things as determining how much cumulative time is spent in a particular
> > function. This information is normally possible to get from the
> > call return processor. However, when doing normal sampling, call/return
> > information is not available, thus necessitating the need for associating
> > samples directly with call paths.
> > 
> > This commit include changes to db-export layer to make this information
> > available for subsequent patches in this change set, but by itself, does
> > not make any changes visible to the user.
> > 
> > Signed-off-by: Chris Phlipot <cphlipot0@...il.com>
> 
> Acked-by: Adrian Hunter <adrian.hunter@...el.com>

Thanks, applied.

- Arnaldo