From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: 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,
mark.rutland@arm.com
Subject: Re: pmu-chain-promotion kvm-unit-test failures in mainline
Date: Wed, 12 Apr 2023 08:39:24 +0100 [thread overview]
Message-ID: <861qkpmtw3.wl-maz@kernel.org> (raw)
In-Reply-To: <cdf922b3-1ac3-438d-8817-6c4d693b1fc3@sirena.org.uk>
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
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: 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,
mark.rutland@arm.com
Subject: Re: pmu-chain-promotion kvm-unit-test failures in mainline
Date: Wed, 12 Apr 2023 08:39:24 +0100 [thread overview]
Message-ID: <861qkpmtw3.wl-maz@kernel.org> (raw)
In-Reply-To: <cdf922b3-1ac3-438d-8817-6c4d693b1fc3@sirena.org.uk>
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
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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 7:39 UTC|newest]
Thread overview: 10+ 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-11 21:15 ` Mark Brown
2023-04-12 7:39 ` Marc Zyngier [this message]
2023-04-12 7:39 ` Marc Zyngier
2023-04-12 8:00 ` Eric Auger
2023-04-12 8:00 ` Eric Auger
2023-04-12 8:48 ` Mark Rutland
2023-04-12 8:48 ` Mark Rutland
2023-04-19 7:30 ` Eric Auger
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=861qkpmtw3.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andrew.jones@linux.dev \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.