From: Mark Rutland <mark.rutland@arm.com>
To: Eric Auger <eauger@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>, Mark Brown <broonie@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Andrew Jones <andrew.jones@linux.dev>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: pmu-chain-promotion kvm-unit-test failures in mainline
Date: Wed, 12 Apr 2023 09:48:59 +0100 [thread overview]
Message-ID: <ZDZwex6uCrEwS6ds@FVFF77S0Q05N> (raw)
In-Reply-To: <84aaa360-3f96-d648-0fe3-cb6667542bc7@redhat.com>
On Wed, Apr 12, 2023 at 10:00:40AM +0200, Eric Auger wrote:
> Hi,
> On 4/12/23 09:39, Marc Zyngier wrote:
> > On Tue, 11 Apr 2023 22:15:02 +0100,
> > Mark Brown <broonie@kernel.org> wrote:
> >>
> >> [1 <text/plain; us-ascii (7bit)>]
> >> Arm's internal test infrastructure has started seeing failures for the
> >> pmu-chain-promption test in kvm-unit-tests on TX2 when running mainline
> >> and kvm-unit-tests commit 2480430a36102f8ea276b3bfb1d64d5dacc23b8f
> >> ("configure: Show the option in case it is not known"). The log I'm
> >> seeing from the test runner is:
> >>
> >> TESTNAME=pmu-chain-promotion TIMEOUT=90s ACCEL= ./arm/run arm/pmu.flat -smp 1 -append 'pmu-chain-promotion'
> >> FAIL pmu-chain-promotion (7 tests, 2 unexpected failures)
> >>
> >> Unfortunately I don't have direct access to a TX2 so can't readily
> >> alter the test run other than replacing the kernel. I believe the
> >> specific failures were:
> >>
> >> FAIL: pmu: pmu-chain-promotion: 32-bit overflows: CHAIN counter enabled: CHAIN counter was incremented and overflow
> >> FAIL: pmu: pmu-chain-promotion: 32-bit overflows: CHAIN counter enabled: 32b->64b CHAIN counter was incremented and overflow
> >
> > Is this related to [1]?
> >
> > M.
> >
> > [1] https://lore.kernel.org/r/20230315110725.1215523-1-eric.auger@redhat.com
>
> Yes please let me know if it fixes your issue. I also tried bisection
> but it did not lead to anything.
FWIW, that worked for me; I replied there with a Tested-by (and test results).
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-12 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 21:15 pmu-chain-promotion kvm-unit-test failures in mainline Mark Brown
2023-04-12 7:39 ` Marc Zyngier
2023-04-12 8:00 ` Eric Auger
2023-04-12 8:48 ` Mark Rutland [this message]
2023-04-19 7:30 ` Eric Auger
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=ZDZwex6uCrEwS6ds@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=andrew.jones@linux.dev \
--cc=broonie@kernel.org \
--cc=eauger@redhat.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@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