From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
sumanthk@linux.ibm.com, hca@linux.ibm.com, svens@linux.ibm.com,
gor@linux.ibm.com
Subject: Re: [PATCH] perf test: fix failing test cases on linux-next for s390
Date: Fri, 16 Jun 2023 18:46:23 -0300 [thread overview]
Message-ID: <ZIzYL2TXf4OqwLaP@kernel.org> (raw)
In-Reply-To: <CAP-5=fXZFgVFMALts+r03c=Xjnv1_iKAx=jqcmRSDU4sDzxSWg@mail.gmail.com>
Em Fri, Jun 16, 2023 at 01:48:45PM -0700, Ian Rogers escreveu:
> On Fri, Jun 16, 2023 at 6:13 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> >
> > Em Fri, Jun 16, 2023 at 10:14:37AM +0200, Thomas Richter escreveu:
> > > In linux-next tree the many test cases fail on s390x when running the
> > > perf test suite, sometime the perf tool dumps core.
> > >
> > > Output before:
> > > 6.1: Test event parsing : FAILED!
> > > 10.3: Parsing of PMU event table metrics : FAILED!
> > > 10.4: Parsing of PMU event table metrics with fake PMUs: FAILED!
> > > 17: Setup struct perf_event_attr : FAILED!
> > > 24: Number of exit events of a simple workload : FAILED!
> > > 26: Object code reading : FAILED!
> > > 28: Use a dummy software event to keep tracking : FAILED!
> > > 35: Track with sched_switch : FAILED!
> > > 42.3: BPF prologue generation : FAILED!
> > > 66: Parse and process metrics : FAILED!
> > > 68: Event expansion for cgroups : FAILED!
> > > 69.2: Perf time to TSC : FAILED!
> > > 74: build id cache operations : FAILED!
> > > 86: Zstd perf.data compression/decompression : FAILED!
> > > 87: perf record tests : FAILED!
> > > 106: Test java symbol : FAILED!
> > >
> > > The reason for all these failure is a missing PMU. On s390x
> > > the PMU is named cpum_cf which is not detected as core PMU.
> > > A similar patch was added before, see
> > > commit 9bacbced0e32 ("perf list: Add s390 support for detailed PMU event description")
> > > which got lost during the recent reworks. Add it again.
> > >
> > > Output after:
> > > 10.2: PMU event map aliases : FAILED!
> > > 42.3: BPF prologue generation : FAILED!
> > >
> > > Most test cases now work and there is not core dump anymore.
> >
> > So you're not fixing 'perf test', that is just what detects the problem,
> > the part being fixed is the PMU code, so I'm rewriting the patch subject
> > to:
> >
> > [PATCH] perf pmu: Fix core PMU detection on s/390
> >
> > Have you bisected the problem to the first patch where this problem
> > appears?
>
> I suspect:
> https://lore.kernel.org/all/20230527072210.2900565-30-irogers@google.com/
> 9d6a1df9b2ee ("perf pmus: Allow just core PMU scanning")
>
> Acked-by: Ian Rogers <irogers@google.com>
I already pushed to perf-tools-next, but this acked/fixes is reachable
via the Link tag.
Thanks for checking and acking!
- Arnaldo
> Thanks,
> Ian
>
> > - Arnaldo
> >
> > > Signed-off-by: Thomas Richter <tmricht@linux.ibm.com>
> > > Cc: Ian Rogers <irogers@google.com>
> > > ---
> > > tools/perf/util/pmu.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> > > index fe64ad292d36..6142e4710a2f 100644
> > > --- a/tools/perf/util/pmu.c
> > > +++ b/tools/perf/util/pmu.c
> > > @@ -1419,7 +1419,7 @@ void perf_pmu__del_formats(struct list_head *formats)
> > >
> > > bool is_pmu_core(const char *name)
> > > {
> > > - return !strcmp(name, "cpu") || is_sysfs_pmu_core(name);
> > > + return !strcmp(name, "cpu") || !strcmp(name, "cpum_cf") || is_sysfs_pmu_core(name);
> > > }
> > >
> > > bool perf_pmu__supports_legacy_cache(const struct perf_pmu *pmu)
> > > --
> > > 2.39.2
> > >
> >
> > --
> >
> > - Arnaldo
--
- Arnaldo
next prev parent reply other threads:[~2023-06-16 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 8:14 [PATCH] perf test: fix failing test cases on linux-next for s390 Thomas Richter
2023-06-16 13:13 ` Arnaldo Carvalho de Melo
2023-06-16 20:48 ` Ian Rogers
2023-06-16 21:46 ` Arnaldo Carvalho de Melo [this message]
2023-06-19 7:58 ` Thomas Richter
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=ZIzYL2TXf4OqwLaP@kernel.org \
--to=acme@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tmricht@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).