linux-kernel - Re: [PATCH v2] perf: add callgrind conversion tool

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] [day] [month] [year] [list]

Date:	Thu, 28 Mar 2013 21:50:41 -0700
From:	Roberto Vitillo <ravitillo@....gov>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	paulus@...ba.org, mingo@...hat.com, acme@...stprotocols.net
Subject: Re: [PATCH v2] perf: add callgrind conversion tool

On Thu, Mar 28, 2013 at 9:18 PM, Namhyung Kim <namhyung@...nel.org> wrote:
> On Thu, Mar 28, 2013 at 04:58:30PM -0700, Sukadev Bhattiprolu wrote:
>> Roberto Vitillo [ravitillo@....gov] wrote:
>> | The proposed patch adds the convert tool to perf which allows to convert a
>> | perf.data file to a set of callgrind data files which can subsequently be
>> | displayed with kcachegrind.
>>
>> Sounds interesting and useful. My only comment is that 'convert' is a
>> generic term and this is converting to a specific format (i.e callgrind).
>> In theory we could have conversions to other formats in the future ?
>
> Maybe we can support converting to CTF or someother formats which have
> nice viewer?

That sounds like a good idea. I could add a -t option to the convert tool
that allows to specify the output format. Initially the tool would have just
the callgrind one but later on we can add support for CTF and possibly
other formats.

Roberto
--
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/