From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Howard Chu <howardchu95@gmail.com>,
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, 23 Dec 2024 16:40:27 -0300 [thread overview]
Message-ID: <Z2m8qzyLdm1BEYuF@x1> (raw)
In-Reply-To: <Z2mzzytPOpjF0Hxe@x1>
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.
- Arnaldo
next prev parent reply other threads:[~2024-12-23 19:40 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 [this message]
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
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=Z2m8qzyLdm1BEYuF@x1 \
--to=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 \
--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).