linux-kernel - [RFC] Adding Support for Firefox's Gecko Profile Format

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

Message-ID: <ZG5kjDN63HqqMuJJ@yoga>
Date:   Thu, 25 May 2023 00:55:00 +0530
From:   Anup Sharma <anupnewsmail@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Jiri Olsa <jolsa@...nel.org>,
        Namhyung Kim <namhyung@...nel.org>,
        Ian Rogers <irogers@...gle.com>,
        Adrian Hunter <adrian.hunter@...el.com>,
        linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC] Adding Support for Firefox's Gecko Profile Format

Hello everyone,

I'm happy to share that I'll be working on adding support for Firefox's Gecko profile format.
This format is utilized by the Firefox profiler, which is a powerful tool for performance analysis
and debugging. By enhancing the perf data command to generate perf.data files in the Gecko
profile format, it will allow us to leverage the capabilities of the Firefox profiler for visualizing
and analyzing the performance data.

As a starter task, I have created a test for testing the perf data JSON converter command.
I'm also looking for a few more starter tasks related to this project. I would greatly appreciate
your advice and guidance.

In my effort to identify any existing bugs, I have enabled flags like 'fsanitize=address' to detect
potential issues but have not found any :). Additionally, I am running perf data commands to ensure
that all use cases are handled properly.

I have one question regarding the installation process. Typically, I navigate to the perf directory,
run 'make', and then cp 'perf' to '/usr/bin'. However, I noticed that by default, perf is installed in
the '~/bin/perf' directory. Could someone please clarify why this is the case? Furthermore, I would
like to know how all of you compile the perf tree.

Thank you for your support and I'm looking forward to collaborating with you on this project!

Regards,
Anup