linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@amd.com>
To: andrii@kernel.org
Cc: Jiri Olsa <jolsa@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: [BUG] perf test: Regression because of d6e6286a12e7
Date: Thu, 6 Jul 2023 10:07:51 +0530	[thread overview]
Message-ID: <ab865e6d-06c5-078e-e404-7f90686db50d@amd.com> (raw)

Hi Andrii,

I'm seeing perf test failure because of commit d6e6286a12e7 ("libbpf:
disassociate section handler on explicit bpf_program__set_type() call").

With 6.4 kernel and perf:

  $ ./tools/perf/perf version
  perf version 6.4.g6995e2de6891
  $ sudo ./tools/perf/perf test 42
   42: BPF filter                               :
   42.1: Basic BPF filtering                    : Ok
   42.2: BPF pinning                            : Ok
   42.3: BPF prologue generation                : FAILED!

After reverting d6e6286a12e7 commit:

  $ git revert d6e6286a12e7
  $ make -C tools/perf/
  $ sudo ./tools/perf/perf test 42
   42: BPF filter                               :
   42.1: Basic BPF filtering                    : Ok
   42.2: BPF pinning                            : Ok
   42.3: BPF prologue generation                : Ok

Is it a known issue?

Thanks,
Ravi

             reply	other threads:[~2023-07-06  4:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  4:37 Ravi Bangoria [this message]
2023-07-07 23:16 ` [BUG] perf test: Regression because of d6e6286a12e7 Andrii Nakryiko
2023-07-10  4:03   ` Ravi Bangoria
2023-07-10 21:36     ` Andrii Nakryiko
2023-07-12 14:08       ` Ravi Bangoria
2023-07-12 15:39         ` Arnaldo Carvalho de Melo
2023-07-12 18:20           ` Alexei Starovoitov
2023-07-13 20:57             ` Arnaldo Carvalho de Melo
2023-07-14 18:15               ` Mykola Lysenko
     [not found]                 ` <SA1PR15MB46099ABDC08009096019B5B4CBF7A@SA1PR15MB4609.namprd15.prod.outlook.com>
2023-09-14 21:54                   ` Ian Rogers
2023-09-17  9:22                   ` Arnaldo Carvalho de Melo

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=ab865e6d-06c5-078e-e404-7f90686db50d@amd.com \
    --to=ravi.bangoria@amd.com \
    --cc=acme@kernel.org \
    --cc=andrii@kernel.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).