All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@gmail.com>
To: uftrace@googlegroups.com, linux-trace-devel@vger.kernel.org
Subject: [ANNOUNCE] uftrace v0.20 is released
Date: Sat, 29 Aug 2026 19:00:07 -0700	[thread overview]
Message-ID: <20260830020008.157705-1-namhyung@gmail.com> (raw)

Hello,

I'm excited to announce that uftrace v0.20 is just released!
This version comes with a lot of new features and bug fixes.
You can get it from the below link:

https://github.com/namhyung/uftrace/releases/tag/v0.20

Now uftrace replay supports 'callsite' trigger action to display
source location of the caller of the current function.  This can be
useful when there are many calls to the same function in a single
function.

    $ uftrace -T getpid@callsite  tests/t-abc
    # DURATION     TID      FUNCTION
       0.558 us [  19501] | __monstartup();
       0.281 us [  19501] | __cxa_atexit();
                [  19501] | main() {
                [  19501] |   a() {
                [  19501] |     b() {
                [  19501] |       c() {
       0.596 us [  19501] |         getpid(); /* from tests/s-abc.c:23 */
       1.083 us [  19501] |       } /* c */
       1.279 us [  19501] |     } /* b */
       1.403 us [  19501] |   } /* a */
       1.583 us [  19501] | } /* main */

And there are new output fields for uftrace report.  They will help to
find important information about the execution.

 * total-max-ts: Timestamp of function entry with maximum total time
 * total-min-ts: Timestamp of function entry with minimum total time
 * self-max-ts: Timestamp of function entry with maximum self time
 * self-min-ts: Timestamp of function entry with minimum self time
 * cpu-count: Number of CPUs that function ran on
 * cpu-list: List of CPUs that function ran on
 * cpu-mask: Bitmask of CPUs that function ran on

Also uftrace dump adds --format option to specify output instead of
the dedicated options like --chrome or --flame-graph.  These options
was deprecated and will be removed in later version.  So please use
uftrace dump --format=chrome instead.

 * available formats: chrome, flame-graph, graphviz, mermaid

In addition, a couple of new scripts were added to generate data in
other formats like:

 * new script: dump-perfetto.py, dump-firefox.py

Other notable changes are improved dynamic tracing on RISC-V, Rust v0
demangler support, uftrace info --system option, Fedora minidebug
format support and command-aware help message.

And there are more bug fixes and improvements.  Thank you all for
making uftrace more useful, efficient and portable!

Namhyung

                 reply	other threads:[~2026-08-30  2:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260830020008.157705-1-namhyung@gmail.com \
    --to=namhyung@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=uftrace@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.