All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Howard Chu <howardchu95@gmail.com>
Subject: Re: [PATCH] perf trace: Skip unnecessary synthesis for summary-only mode
Date: Tue, 31 Mar 2026 00:07:52 -0700	[thread overview]
Message-ID: <actyyLHzGLK7jWkH@google.com> (raw)
In-Reply-To: <CAP-5=fV0SKCOtYoJGUuui116wnbowZFcDu18tvrBQTiCF_5g3w@mail.gmail.com>

On Mon, Mar 30, 2026 at 02:00:08PM -0700, Ian Rogers wrote:
> On Mon, Mar 30, 2026 at 1:14 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > It needs to synthesize task info for the comm name.  The mmap
> > information is only needed for callchain symbolization which is not used
> > by the summary mode.  Also total or cgroup summary mode don't require
> > the task info.  Let's skip the processing if possible.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> >  tools/perf/builtin-trace.c | 22 +++++++++++++++++-----
> >  1 file changed, 17 insertions(+), 5 deletions(-)
> >
> > diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> > index f487fbaa0ad60028..d09d78b3222717d1 100644
> > --- a/tools/perf/builtin-trace.c
> > +++ b/tools/perf/builtin-trace.c
> > @@ -2004,11 +2004,23 @@ static int trace__symbols_init(struct trace *trace, int argc, const char **argv,
> >         if (err < 0)
> >                 goto out;
> >
> > -       err = __machine__synthesize_threads(trace->host, &trace->tool, &trace->opts.target,
> > -                                           evlist->core.threads, trace__tool_process,
> > -                                           /*needs_mmap=*/callchain_param.enabled,
> > -                                           /*mmap_data=*/false,
> > -                                           /*nr_threads_synthesize=*/1);
> > +       if (trace->summary_only) {
> > +               if (trace->summary_mode == SUMMARY__BY_THREAD) {
> > +                       err = __machine__synthesize_threads(trace->host, &trace->tool,
> > +                                                           &trace->opts.target,
> > +                                                           evlist->core.threads,
> > +                                                           trace__tool_process,
> > +                                                           /*needs_mmap=*/false,
> > +                                                           /*mmap_data=*/false,
> > +                                                           /*nr_threads_synthesize=*/1);
> > +               }
> > +       } else {
> > +               err = __machine__synthesize_threads(trace->host, &trace->tool, &trace->opts.target,
> > +                                                   evlist->core.threads, trace__tool_process,
> > +                                                   /*needs_mmap=*/callchain_param.enabled,
> > +                                                   /*mmap_data=*/false,
> > +                                                   /*nr_threads_synthesize=*/1);
> > +       }
> 
> Could this be simplified to something like:
> ```
> if (!trace->summary_only || trace->summary_mode == SUMMARY__BY_THREAD) {
>        err = __machine__synthesize_threads(trace->host, &trace->tool,
> &trace->opts.target,
>                                            evlist->core.threads,
> trace__tool_process,
> 
> /*needs_mmap=*/callchain_param.enabled && !trace->summary_only,
>                                            /*mmap_data=*/false,
>                                            /*nr_threads_synthesize=*/1);
> }
> ```

Looks good, will update.

Btw, it'd be nice if you could find a mail client that can turn off the
line wrapping. :)

Thanks,
Namhyung


      reply	other threads:[~2026-03-31  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 20:14 [PATCH] perf trace: Skip unnecessary synthesis for summary-only mode Namhyung Kim
2026-03-30 21:00 ` Ian Rogers
2026-03-31  7:07   ` Namhyung Kim [this message]

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=actyyLHzGLK7jWkH@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@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 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.