From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: alice.mei.rogers@gmail.com, namhyung@kernel.org,
adrian.hunter@intel.com, jolsa@kernel.org, laixintaoo@gmail.com,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org
Subject: Re: [PATCH v4 0/2] perf python TUI report and flamegraph
Date: Wed, 9 Sep 2026 17:30:28 -0300 [thread overview]
Message-ID: <aqHB5PahbbxmXBO-@x2> (raw)
In-Reply-To: <20260809051820.2436530-1-irogers@google.com>
On Sat, Aug 08, 2026 at 10:18:17PM -0700, Ian Rogers wrote:
> Implement a perf TUI using the python textual module. Using the
> textual framework means that in most modern terminals the mouse is
> supported, the color scheme can be configured, and screenshots made.
>
> The work is dependent on the extensions to the perf python module
> merged into perf-tools-next such as commit 88439191ad5e ("perf python:
> Add callchain support"). It is also dependent on the python textual
> module for TUI support.
Cool stuff, just tested it :-)
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
> v4: Fix typo of profle to profile and tweak argparse command
> description to only mention flamegraph after that support is added
> (Sashiko). Sashiko notes a high severity issue because the script
> depends on perf Python module extensions that are already
> merged. This is because Sashiko is testing the changes against the
> perf-tools rather than perf-tools-next. Verified
> rich.errors.MarkupError don't occur for kernel DSOs, primarily as
> there is always a space after the square brackets.
>
> v3: Tweaks to commit messages (Sashiko).
> https://lore.kernel.org/linux-perf-users/20260809041638.2402705-1-irogers@google.com/
>
> v2: Migrate from inbuilt perf python interpreter to perf python
> module. Improve the flamegraph performance. Use the textual's
> color scheme rather than red and white.
> https://lore.kernel.org/linux-perf-users/20260808065743.2328212-1-irogers@google.com/
>
> v1:
> https://lore.kernel.org/linux-perf-users/20250725082425.20999-1-irogers@google.com/
>
> Alice Rogers (2):
> perf python: New treport script
> perf python: treport add flamegraph support
>
> tools/perf/python/treport.py | 561 +++++++++++++++++++++++++++++++++++
> 1 file changed, 561 insertions(+)
> create mode 100755 tools/perf/python/treport.py
>
> --
> 2.55.0.654.g21b8a5bc05-goog
next prev parent reply other threads:[~2026-09-09 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 8:24 [PATCH v1 1/2] perf script: New treport script Ian Rogers
2025-07-25 8:24 ` [PATCH v1 2/2] perf script: treport add flamegraph support Ian Rogers
2025-07-25 8:38 ` Ian Rogers
2026-08-08 6:57 ` [PATCH v2 0/2] perf python TUI report and flamegraph Ian Rogers
2026-08-08 6:57 ` [PATCH v2 1/2] perf python: New treport script Ian Rogers
2026-08-08 6:57 ` [PATCH v2 2/2] perf python: treport add flamegraph support Ian Rogers
2026-08-09 4:16 ` [PATCH v3 0/2] perf python TUI report and flamegraph Ian Rogers
2026-08-09 4:16 ` [PATCH v3 1/2] perf python: New treport script Ian Rogers
2026-08-09 4:16 ` [PATCH v3] perf test: Fixes for check branch stack sampling Ian Rogers
2026-08-09 5:21 ` Ian Rogers
2026-08-09 4:16 ` [PATCH v3 2/2] perf python: treport add flamegraph support Ian Rogers
2026-08-09 5:18 ` [PATCH v4 0/2] perf python TUI report and flamegraph Ian Rogers
2026-08-09 5:18 ` [PATCH v4 1/2] perf python: New treport script Ian Rogers
2026-08-09 5:18 ` [PATCH v4 2/2] perf python: treport add flamegraph support Ian Rogers
2026-09-09 20:30 ` Arnaldo Carvalho de Melo [this message]
2025-07-26 6:43 ` [PATCH v1 2/2] perf script: " Namhyung Kim
2025-07-26 6:39 ` [PATCH v1 1/2] perf script: New treport script Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aqHB5PahbbxmXBO-@x2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alice.mei.rogers@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=laixintaoo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®