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
Subject: Re: [PATCH v2 4/4] perf test: Update PE file test for other locations
Date: Mon, 12 Oct 2026 16:06:24 -0700 [thread overview]
Message-ID: <as1n8CgDZxYlQkSK@google.com> (raw)
In-Reply-To: <CAP-5=fW1SSoyGKjaujZewF=b3rJ-0vp4kJ-friWNzOQWk+ki5A@mail.gmail.com>
On Mon, Oct 12, 2026 at 02:51:52PM -0700, Ian Rogers wrote:
> On Sun, Oct 11, 2026 at 10:30 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > The test__pe_file_parsing() expects the test is in the tools/perf
> > directory, but it could be root or a separate build directory. Let's
> > update the logic to try other paths like in the shell_tests__dir_fd().
> >
> > Also add some debug messages to inform users why it's skipped.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/tests/pe-file-parsing.c | 13 +++++++++++--
> > 1 file changed, 11 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/perf/tests/pe-file-parsing.c b/tools/perf/tests/pe-file-parsing.c
> > index 3979f38bf127c218..78dae7e43603b9f8 100644
> > --- a/tools/perf/tests/pe-file-parsing.c
> > +++ b/tools/perf/tests/pe-file-parsing.c
> > @@ -74,10 +74,17 @@ static int test__pe_file_parsing(struct test_suite *test __maybe_unused,
> > {
> > struct stat st;
> > char path_dir[PATH_MAX];
> > + static const char * const tests_dirs[] = {
> > + "./tools/perf/tests",
> > + "./tests",
> > + "./source/tests"
>
> I'm not sure where "source/tests" comes from?
AFAIK it's set when you pass O=$(DIR) option when you build perf and it
points the source tree.
> nit: could we add the exec_path case to the list?
It's checked right after. :)
Thanks,
Namhyung
>
> Thanks,
> Ian
>
> > + };
> >
> > /* First try development tree tests. */
> > - if (!lstat("./tests", &st))
> > - return run_dir("./tests");
> > + for (size_t i = 0; i < ARRAY_SIZE(tests_dirs); ++i) {
> > + if (!lstat(tests_dirs[i], &st))
> > + return run_dir(tests_dirs[i]);
> > + }
> >
> > /* Then installed path. */
> > snprintf(path_dir, PATH_MAX, "%s/tests", get_argv_exec_path());
> > @@ -85,6 +92,7 @@ static int test__pe_file_parsing(struct test_suite *test __maybe_unused,
> > if (!lstat(path_dir, &st))
> > return run_dir(path_dir);
> >
> > + pr_debug("cannot find the tests directory\n");
> > return TEST_SKIP;
> > }
> >
> > @@ -93,6 +101,7 @@ static int test__pe_file_parsing(struct test_suite *test __maybe_unused,
> > static int test__pe_file_parsing(struct test_suite *test __maybe_unused,
> > int subtest __maybe_unused)
> > {
> > + pr_debug("libbfd is not available\n");
> > return TEST_SKIP;
> > }
> >
> > --
> > 2.55.0
> >
next prev parent reply other threads:[~2026-10-12 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 5:30 [PATCH v2 1/4] perf symbol: Fix symbol loading from libbfd Namhyung Kim
2026-10-12 5:30 ` [PATCH v2 2/4] perf symbol: Add missing symsrc__destroy() for libbfd Namhyung Kim
2026-10-12 5:36 ` sashiko-bot
2026-10-12 21:53 ` Ian Rogers
2026-10-12 5:30 ` [PATCH v2 3/4] perf symbol: Set dso symtab type " Namhyung Kim
2026-10-12 5:40 ` sashiko-bot
2026-10-12 19:36 ` Namhyung Kim
2026-10-12 5:30 ` [PATCH v2 4/4] perf test: Update PE file test for other locations Namhyung Kim
2026-10-12 5:38 ` sashiko-bot
2026-10-12 19:42 ` Namhyung Kim
2026-10-12 21:51 ` Ian Rogers
2026-10-12 23:06 ` Namhyung Kim [this message]
2026-10-12 23:11 ` Ian Rogers
2026-10-12 23:37 ` Namhyung Kim
2026-10-12 5:37 ` [PATCH v2 1/4] perf symbol: Fix symbol loading from libbfd sashiko-bot
2026-10-12 21:52 ` Ian Rogers
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=as1n8CgDZxYlQkSK@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox