From: Miguel Luis <miguel.luis@oracle.com>
To: Sebastian Ott <sebott@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Colton Lewis <coltonlewis@google.com>,
Ricardo Koller <ricarkol@google.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>, Shuah Khan <shuah@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] KVM: arm64: selftests: arch_timer_edge_cases fixes
Date: Mon, 9 Jun 2025 17:26:35 +0000 [thread overview]
Message-ID: <B77F70F2-EECA-4E10-9F00-972F6AE27831@oracle.com> (raw)
In-Reply-To: <20250605103613.14544-1-sebott@redhat.com>
Hi Sebastian,
Thanks in advance.
> On 5 Jun 2025, at 10:36, Sebastian Ott <sebott@redhat.com> wrote:
>
> Some small fixes for arch_timer_edge_cases that I stumbled upon
> while debugging failures for this selftest on ampere-one.
>
I’ve tested this test under three circumstances:
1) Original (!HAS_EL2 && !HAS_EL2_E2H0)
2) HAS_EL2 && HAS_EL2_E2H0
3) HAS_EL2 && !HAS_EL2_E2H0
Tests 1) and 2) returned in approx. the same amount of real time (about 12s) although 3) doesn’t
seem to return at all.
I’ve tested it on ampere-one.
Miguel
> Changes since v1:
> * determine effective counter width based on suggestions from Marc
> Changes since v2:
> * new patch to fix xval initialization
>
> I've done tests with this on various machines - no issues during
> several hundreds of test runs.
>
> v1: https://lore.kernel.org/kvmarm/20250509143312.34224-1-sebott@redhat.com/
> v2: https://lore.kernel.org/kvmarm/20250527142434.25209-1-sebott@redhat.com/
>
> Sebastian Ott (4):
> KVM: arm64: selftests: fix help text for arch_timer_edge_cases
> KVM: arm64: selftests: fix thread migration in arch_timer_edge_cases
> KVM: arm64: selftests: arch_timer_edge_cases - fix xval init
> KVM: arm64: selftests: arch_timer_edge_cases - determine effective counter width
>
> .../kvm/arm64/arch_timer_edge_cases.c | 39 ++++++++++++-------
> 1 file changed, 25 insertions(+), 14 deletions(-)
>
>
> base-commit: 0ff41df1cb268fc69e703a08a57ee14ae967d0ca
> --
> 2.49.0
>
>
next prev parent reply other threads:[~2025-06-09 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 10:36 Sebastian Ott
2025-06-05 10:36 ` [PATCH v3 1/4] KVM: arm64: selftests: fix help text for arch_timer_edge_cases Sebastian Ott
2025-06-05 10:36 ` [PATCH v3 2/4] KVM: arm64: selftests: fix thread migration in arch_timer_edge_cases Sebastian Ott
2025-06-05 10:36 ` [PATCH v3 3/4] KVM: arm64: selftests: arch_timer_edge_cases - fix xval init Sebastian Ott
2025-06-05 10:36 ` [PATCH v3 4/4] KVM: arm64: selftests: arch_timer_edge_cases - determine effective counter width Sebastian Ott
2025-06-05 13:33 ` [PATCH v3 0/4] KVM: arm64: selftests: arch_timer_edge_cases fixes Marc Zyngier
2025-06-09 17:26 ` Miguel Luis [this message]
2025-06-10 13:50 ` Sebastian Ott
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=B77F70F2-EECA-4E10-9F00-972F6AE27831@oracle.com \
--to=miguel.luis@oracle.com \
--cc=coltonlewis@google.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ricarkol@google.com \
--cc=sebott@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®