From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: kvmarm@lists.linux.dev,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Fuad Tabba <tabba@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>,
Mark Brown <broonie@kernel.org>,
Aishwarya TCV <Aishwarya.TCV@arm.com>
Subject: Re: kvm-unit-tests hang on Arm FVP with protected mode
Date: Fri, 05 Sep 2025 13:42:07 +0100 [thread overview]
Message-ID: <87ms79ystc.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+G9fYsT3b3Qd-m6tSDOgAXpgLPWz0QD_Z6a+_ff4oTecA85PQ@mail.gmail.com>
On Fri, 05 Sep 2025 13:28:45 +0100,
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> kvm-unit-tests consistently hang on Arm FVP when booted with
> kvm-arm.mode=protected across both 4K and 64K page-size kernel builds.
>
> Running the same tests with kvm-arm.mode=vhe completes successfully.
Do you realise that "kvm-arm.mode=vhe" is not a valid option?
>
> Anders, bisected and identified the first bad commit as:
>
> 066daa8d3bc2694c392e14091978043aed7b1f23
> KVM: arm64: Initialize HCRX_EL2 traps in pKVM
>
> Regression Analysis:
> - Reproducibility? yes
>
> Test regression: kvm-unit-tests hang on Arm FVP with kvm-arm.mode=protected
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Environment:
> Platform: Arm FVP base-revc
> Kernel: arm64 (tested with 4K and 64K page sizes)
> Mode: kvm-arm.mode=protected (hangs) vs kvm-arm.mode=vhe (passes)
> Test suite: kvm-unit-tests (./run_tests.sh -a -t -v)
> Cmdline args : kvm-arm.mode=protected
> Kernel: Mainline master and Linux next master
>
> Test run log:
> INFO: running kvm unit tests ...
> + [ True = false ]
> + ./run_tests.sh -a -t -v
> + tee -a /lava-1/0/tests/0_kvm-unit-tests/automated/linux/kvm-unit-tests/output/result_log.txt
> TAP version 13
What do you expect us to do with such a non-report? Can you please, at
the very least, identify which test in that test suite triggers the
failure?
> Links:
> https://regressions.linaro.org/lkft/linux-mainline-master/v6.17-rc4/lava/kvm-unit-tests/history/?page=1
What is there? This link requires a login, and goes to 11 on the
scale of being useless.
M.
--
Jazz isn't dead. It just smells funny.
next prev parent reply other threads:[~2025-09-05 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 12:28 kvm-unit-tests hang on Arm FVP with protected mode Naresh Kamboju
2025-09-05 12:42 ` Marc Zyngier [this message]
2025-09-05 13:38 ` Mark Brown
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=87ms79ystc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Aishwarya.TCV@arm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@linaro.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=tabba@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