From: Namhyung Kim <namhyung@kernel.org>
To: Howard Chu <howardchu95@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace
Date: Mon, 3 Feb 2025 19:16:53 -0800 [thread overview]
Message-ID: <Z6GGpcTMvw5z6A5V@google.com> (raw)
In-Reply-To: <CAH0uvoit+6nhADW_d61VcaSE17Wp5DH7BtUVjQdT=kU9rMqaaA@mail.gmail.com>
On Fri, Jan 31, 2025 at 04:14:09PM -0800, Howard Chu wrote:
> Hello Namhyung,
>
> Sorry for somehow missing this reply...
>
> On Thu, Jan 23, 2025 at 3:53 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > On Tue, Jan 21, 2025 at 04:19:35PM -0800, Howard Chu wrote:
> > > Hello Namhyung,
> > >
> > > On Sat, Jan 18, 2025 at 10:28 AM Namhyung Kim <namhyung@kernel.org> wrote:
> > > >
> > > > On Mon, Jan 13, 2025 at 12:57:23PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > > On Fri, Jan 10, 2025 at 04:52:08PM -0800, Howard Chu wrote:
> > > > > > Hello Arnaldo,
> > > > > >
> > > > > > On Mon, Dec 23, 2024 at 11:40 AM Arnaldo Carvalho de Melo
> > > > > > <acme@kernel.org> wrote:
> > > > > > >
> > > > > > > On Mon, Dec 23, 2024 at 04:02:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > > > > > On Mon, Dec 16, 2024 at 11:58:46AM -0800, Namhyung Kim wrote:
> > > > > > > > > On Sun, Dec 15, 2024 at 11:07:09AM -0800, Howard Chu wrote:
> > > > > > > > > > Changes in v4:
> > > > > > > > > > - Use if -f to check the existence of vmlinux BTF, and exit if it
> > > > > > > > > > doesn't, so trace_test_string will not overwrite $err, and keep
> > > > > > > > > > running the test.
> > > > > > > > > >
> > > > > > > > > > Changes in v3:
> > > > > > > > > > - Add vmlinux BTF check, and skip the tests if it doesn't exist
> > > > > > > > > >
> > > > > > > > > > v1, v2:
> > > > > > > > > >
> > > > > > > > > > The previous version of the perf trace BTF general augmentation tests
> > > > > > > > > > didn't pass Shellcheck (thanks to Arnaldo Carvalho de Melo
> > > > > > > > > > <acme@kernel.org> for pointing this out), this version uses bash instead
> > > > > > > > > > of POSIX shell to pass Shellcheck.
> > > > > > > > > >
> > > > > > > > > > This patch series also adds documentation for the new option
> > > > > > > > > > --force-btf, which is used in the tests.
> > > > > > > > > >
> > > > > > > > > > Link: https://lore.kernel.org/linux-perf-users/Zt9yiQq-n-W6I274@x1/
> > > > > > > > > >
> > > > > > > > > > Howard Chu (2):
> > > > > > > > > > perf trace: Add tests for BTF general augmentation
> > > > > > > > > > perf docs: Add documentation for --force-btf option
> > > > > > > > >
> > > > > > > > > Acked-by: Namhyung Kim <namhyung@kernel.org>
> > > > > > > >
> > > > > > > > Thanks, applied to perf-tools-next,
> > > > > > >
> > > > > > > It fails when running in parallel mode, sometimes:
> > > > > > >
> > > > > > > 109: perf trace BTF general tests : FAILED!
> > > > > > >
> > > > > > > Then:
> > > > > > >
> > > > > > > root@number:~# perf stat --null -r 10 perf test "BTF general"
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : FAILED!
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : FAILED!
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > > 109: perf trace BTF general tests : Ok
> > > > > > >
> > > > > > > Performance counter stats for 'perf test BTF general' (10 runs):
> > > > > > >
> > > > > > > 2.148 +- 0.293 seconds time elapsed ( +- 13.63% )
> > > > > > >
> > > > > > > root@number:~#
> > > > > > >
> > > > > > >
> > > > > > > So its not just when running in paralell, anyway, its merged, we can go
> > > > > > > on from what we got there.
> > > > > >
> > > > > > It never fails on my machine, I think the reason is my machine is not
> > > > > > fully-loaded. Can you please run
> > > > > > ```
> > > > > > perf stat --null -r 10 perf test -vv "BTF general"
> > > > > > ```
> > > > > > And provide the output?
> > > > >
> > > > > root@number:~# grep -m1 'model name' /proc/cpuinfo
> > > > > model name : Intel(R) Core(TM) i7-14700K
> > > > > root@number:~#
> > > > >
> > > > > root@number:~# perf stat --null -r 10 perf test -vv "BTF general"
> > > > > 106: perf trace BTF general tests:
> > > > > --- start ---
> > > > > test child forked, pid 47824
> > > > > Checking if vmlinux BTF exists
> > > > > Testing perf trace's string augmentation
> > > > > String augmentation test failed
> > > > > ---- end(-1) ----
> > > > > 106: perf trace BTF general tests : FAILED!
> > > > > 106: perf trace BTF general tests:
> > > > > --- start ---
> > > > > test child forked, pid 47842
> > > > > Checking if vmlinux BTF exists
> > > > > Testing perf trace's string augmentation
> > > > > String augmentation test failed
> > > > > ---- end(-1) ----
> > > > > 106: perf trace BTF general tests : FAILED!
> > > > > ...
> > > >
> > > > I also see the failure on not fully-loaded machines (both Intel and
> > > > AMD).
> > > >
> > > > $ sudo ./perf test -v BTF
> > > > --- start ---
> > > > test child forked, pid 525025
> > > > Checking if vmlinux BTF exists
> > > > Testing perf trace's string augmentation
> > > > String augmentation test failed
> > > > ---- end(-1) ----
> > > > 106: perf trace BTF general tests : FAILED!
> > > >
> > > > Thanks,
> > > > Namhyung
> > > >
> > >
> > > Just wondering, did you and Arnaldo apply this patch:
> > > https://lore.kernel.org/linux-perf-users/20241213023047.541218-1-howardchu95@gmail.com/
> >
> > I don't think we applied it, will add to perf-tools.
> >
> > >
> > > This seems to solve the problem for me...
> >
> > But I'm not sure if it fixes the problem. IIUC the patch fixes the
> > loading problem.
>
> Yes. However, if the machine is unable to load the BPF program, the
> error message will be:
>
> perf $ sudo ./perf test general -v
> --- start ---
> test child forked, pid 173990
> Checking if vmlinux BTF exists
> Testing perf trace's string augmentation
> String augmentation test failed
> ---- end(-1) ----
> 106: perf trace BTF general tests : FAILED!
>
> Which is indistinguishable from an actual string augmentation error
> that has a string mismatch...
Ok, that's not good.
>
> > And for some reason, I don't see the problem any more.
> > But I remember this sometimes happened in the past.
>
> Do you mean that perf trace breaks occasionally? This sounds urgent.
> Could you please provide me with your kernel version and Clang
> version? Thank you very much! :)
Yep, sometimes it works and sometimes it failed to load the BPF.
The kernel version of this laptop is v6.10.11 and clang version is
16.0.6.
Thanks,
Namhyung
prev parent reply other threads:[~2025-02-04 3:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 19:07 [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace Howard Chu
2024-12-15 19:07 ` [PATCH v4 1/2] perf trace: Add tests for BTF general augmentation Howard Chu
2024-12-15 19:07 ` [PATCH v4 2/2] perf docs: Add documentation for --force-btf option Howard Chu
2024-12-23 19:06 ` Arnaldo Carvalho de Melo
2024-12-16 19:58 ` [PATCH v4 0/2] perf trace: Add more tests for BTF-augmented perf trace Namhyung Kim
2024-12-23 19:02 ` Arnaldo Carvalho de Melo
2024-12-23 19:40 ` Arnaldo Carvalho de Melo
2024-12-24 2:03 ` Howard Chu
2024-12-26 15:17 ` Arnaldo Carvalho de Melo
2025-01-11 0:52 ` Howard Chu
2025-01-13 15:57 ` Arnaldo Carvalho de Melo
2025-01-18 18:28 ` Namhyung Kim
2025-01-22 0:19 ` Howard Chu
2025-01-23 23:53 ` Namhyung Kim
2025-02-01 0:14 ` Howard Chu
2025-02-04 3:16 ` 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=Z6GGpcTMvw5z6A5V@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox