From: Andrew Jones <andrew.jones@linux.dev>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, kvm@vger.kernel.org,
kvmarm@lists.linux.dev, maz@kernel.org, will@kernel.org,
oliver.upton@linux.dev, ricarkol@google.com, reijiw@google.com,
alexandru.elisei@arm.com, mark.rutland@arm.com
Subject: Re: [kvm-unit-tests PATCH v2 0/6] arm: pmu: Fix random failures of pmu-chain-promotion
Date: Wed, 7 Jun 2023 21:07:09 +0200 [thread overview]
Message-ID: <20230607-a12c8e1d270b53e522756648@orel> (raw)
In-Reply-To: <20230531201438.3881600-1-eric.auger@redhat.com>
On Wed, May 31, 2023 at 10:14:32PM +0200, Eric Auger wrote:
> On some HW (ThunderXv2), some random failures of
> pmu-chain-promotion test can be observed.
>
> pmu-chain-promotion is composed of several subtests
> which run 2 mem_access loops. The initial value of
> the counter is set so that no overflow is expected on
> the first loop run and overflow is expected on the second.
> However it is observed that sometimes we get an overflow
> on the first run. It looks related to some variability of
> the mem_acess count. This variability is observed on all
> HW I have access to, with different span though. On
> ThunderX2 HW it looks the margin that is currently taken
> is too small and we regularly hit failure.
>
> although the first goal of this series is to increase
> the count/margin used in those tests, it also attempts
> to improve the pmu-chain-promotion logs, add some barriers
> in the mem-access loop, clarify the chain counter
> enable/disable sequence.
>
> A new 'pmu-mem-access-reliability' is also introduced to
> detect issues with MEM_ACCESS event variability and make
> the debug easier.
>
> Obviously one can wonder if this variability is something normal
> and does not hide any other bug. I hope this series will raise
> additional discussions about this.
>
> https://github.com/eauger/kut/tree/pmu-chain-promotion-fixes-v2
>
> History:
> v1 -> v2:
> - Take into account Alexandru's & Mark's comments. Added some
> R-b's and T-b's.
>
> Eric Auger (6):
> arm: pmu: pmu-chain-promotion: Improve debug messages
> arm: pmu: pmu-chain-promotion: Introduce defines for count and margin
> values
> arm: pmu: Add extra DSB barriers in the mem_access loop
> arm: pmu: Fix chain counter enable/disable sequences
> arm: pmu: Add pmu-mem-access-reliability test
> arm: pmu-chain-promotion: Increase the count and margin values
>
> arm/pmu.c | 196 +++++++++++++++++++++++++++++++++-------------
> arm/unittests.cfg | 6 ++
> 2 files changed, 148 insertions(+), 54 deletions(-)
>
> --
> 2.38.1
>
Hi Eric,
I'm eager to merge this, but I'll give Alexandru some time to revisit it
since he had comments on the last revision.
Thanks,
drew
next parent reply other threads:[~2023-06-07 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230531201438.3881600-1-eric.auger@redhat.com>
2023-06-07 19:07 ` Andrew Jones [this message]
2023-06-08 16:38 ` [kvm-unit-tests PATCH v2 0/6] arm: pmu: Fix random failures of pmu-chain-promotion Alexandru Elisei
[not found] ` <20230531201438.3881600-4-eric.auger@redhat.com>
2023-06-16 9:42 ` [kvm-unit-tests PATCH v2 3/6] arm: pmu: Add extra DSB barriers in the mem_access loop Alexandru Elisei
[not found] ` <20230531201438.3881600-5-eric.auger@redhat.com>
2023-06-16 10:50 ` [kvm-unit-tests PATCH v2 4/6] arm: pmu: Fix chain counter enable/disable sequences Alexandru Elisei
2023-06-19 19:57 ` Eric Auger
[not found] ` <20230531201438.3881600-6-eric.auger@redhat.com>
2023-06-16 11:52 ` [kvm-unit-tests PATCH v2 5/6] arm: pmu: Add pmu-mem-access-reliability test Alexandru Elisei
2023-06-19 20:00 ` Eric Auger
2023-06-30 14:43 ` Alexandru Elisei
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=20230607-a12c8e1d270b53e522756648@orel \
--to=andrew.jones@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=reijiw@google.com \
--cc=ricarkol@google.com \
--cc=will@kernel.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