From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Marco Elver <elver@google.com>, Jiri Olsa <jolsa@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf test: Skip sigtrap test on old kernels
Date: Tue, 6 Sep 2022 11:31:04 -0700 [thread overview]
Message-ID: <CAM9d7ci2ZujdY75DUtZA+f=fru7yh8VJrj8-r2RgZetu57u61A@mail.gmail.com> (raw)
In-Reply-To: <YxdA1CVzy9hzE3i1@kernel.org>
On Tue, Sep 6, 2022 at 5:45 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> Em Sat, Sep 03, 2022 at 08:52:01AM +0200, Marco Elver escreveu:
> > On Sat, 3 Sept 2022 at 02:02, Namhyung Kim <namhyung@kernel.org> wrote:
> > >
> > > If it runs on an old kernel, perf_event_open would fail because of the
> > > new fields sigtrap and sig_data. Just skip the test if it failed.
> > >
> > > Cc: Marco Elver <elver@google.com>
> > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > > ---
> > > tools/perf/tests/sigtrap.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/tools/perf/tests/sigtrap.c b/tools/perf/tests/sigtrap.c
> > > index e32ece90e164..7057566e6ae4 100644
> > > --- a/tools/perf/tests/sigtrap.c
> > > +++ b/tools/perf/tests/sigtrap.c
> > > @@ -140,6 +140,7 @@ static int test__sigtrap(struct test_suite *test __maybe_unused, int subtest __m
> > > fd = sys_perf_event_open(&attr, 0, -1, -1, perf_event_open_cloexec_flag());
> > > if (fd < 0) {
> > > pr_debug("FAILED sys_perf_event_open(): %s\n", str_error_r(errno, sbuf, sizeof(sbuf)));
> > > + ret = TEST_SKIP;
> >
> > Wouldn't we be interested if perf_event_open() fails because it could
> > actually be a bug? By skipping we'll be more likely to miss the fact
> > there's a real problem.
> >
> > That's my naive thinking at least - what do other perf tests usually
> > do in this case?
>
> Yeah, I was going to try and check if this is the only way that, with
> the given arguments, perf_event_open would fail, but its better to at
> least check errno against -EINVAL or something?
EINVAL would be too generic and the kernel returns it in many places.
I really wish we could have a better error reporting mechanism.
Maybe we could retry perf_event_open with sigtrap and sig_data cleared.
If it succeeded, then we can skip the test. If it still failed, then report
the error. But it still couldn't find a bug in the sigtrap code.
What do you think?
Thanks,
Namhyung
next prev parent reply other threads:[~2022-09-06 18:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 0:02 [PATCH] perf test: Skip sigtrap test on old kernels Namhyung Kim
2022-09-03 6:52 ` Marco Elver
2022-09-06 12:45 ` Arnaldo Carvalho de Melo
2022-09-06 18:31 ` Namhyung Kim [this message]
2022-09-06 20:50 ` Marco Elver
2022-09-06 20:56 ` Arnaldo Carvalho de Melo
2022-09-06 22:52 ` Namhyung Kim
2022-09-26 15:06 ` James Clark
2022-09-26 16:19 ` Namhyung Kim
2022-09-27 8:48 ` James Clark
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='CAM9d7ci2ZujdY75DUtZA+f=fru7yh8VJrj8-r2RgZetu57u61A@mail.gmail.com' \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=elver@google.com \
--cc=irogers@google.com \
--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;
as well as URLs for NNTP newsgroup(s).