From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Jiri Olsa <jolsa@redhat.com>, Ian Rogers <irogers@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf record: Fix synthesis failure warnings
Date: Thu, 8 Sep 2022 15:58:18 -0300 [thread overview]
Message-ID: <Yxo7SkkijJj1vuZW@kernel.org> (raw)
In-Reply-To: <CAM9d7cj=yyfmCRfEVvp7kCHRE8cTEkRFf_unThde2kNoo-x+GA@mail.gmail.com>
Em Wed, Sep 07, 2022 at 10:58:58AM -0700, Namhyung Kim escreveu:
> On Wed, Sep 7, 2022 at 9:25 AM Adrian Hunter <adrian.hunter@intel.com> wrote:
> >
> > Some calls to synthesis functions set err < 0 but only warn about the
> > failure and continue. However they do not set err back to zero, relying
> > on subsequent code to do that.
> >
> > That changed with the introduction of option --synth. When --synth=no
> > subsequent functions that set err back to zero are not called.
> >
> > Fix by setting err = 0 in those cases.
> >
> > Example:
> >
> > Before:
> >
> > $ perf record --no-bpf-event --synth=all -o /tmp/huh uname
> > Couldn't synthesize bpf events.
> > Linux
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.014 MB /tmp/huh (7 samples) ]
> > $ perf record --no-bpf-event --synth=no -o /tmp/huh uname
> > Couldn't synthesize bpf events.
> >
> > After:
> >
> > $ perf record --no-bpf-event --synth=no -o /tmp/huh uname
> > Couldn't synthesize bpf events.
> > Linux
> > [ perf record: Woken up 1 times to write data ]
> > [ perf record: Captured and wrote 0.014 MB /tmp/huh (7 samples) ]
> >
> > Fixes: 41b740b6e8a9 ("perf record: Add --synth option")
> > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied.
- Arnaldo
> Thanks,
> Namhyung
>
>
> > ---
> > tools/perf/builtin-record.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> > index bce8c941d558..7713246a393f 100644
> > --- a/tools/perf/builtin-record.c
> > +++ b/tools/perf/builtin-record.c
> > @@ -1974,14 +1974,18 @@ static int record__synthesize(struct record *rec, bool tail)
> >
> > err = perf_event__synthesize_bpf_events(session, process_synthesized_event,
> > machine, opts);
> > - if (err < 0)
> > + if (err < 0) {
> > pr_warning("Couldn't synthesize bpf events.\n");
> > + err = 0;
> > + }
> >
> > if (rec->opts.synth & PERF_SYNTH_CGROUP) {
> > err = perf_event__synthesize_cgroups(tool, process_synthesized_event,
> > machine);
> > - if (err < 0)
> > + if (err < 0) {
> > pr_warning("Couldn't synthesize cgroup events.\n");
> > + err = 0;
> > + }
> > }
> >
> > if (rec->opts.nr_threads_synthesize > 1) {
> > --
> > 2.25.1
> >
--
- Arnaldo
prev parent reply other threads:[~2022-09-08 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 16:24 [PATCH] perf record: Fix synthesis failure warnings Adrian Hunter
2022-09-07 17:58 ` Namhyung Kim
2022-09-08 18:58 ` Arnaldo Carvalho de Melo [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=Yxo7SkkijJj1vuZW@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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