[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ms79ystc.wl-maz@kernel.org>
Date: Fri, 05 Sep 2025 13:42:07 +0100
From: Marc Zyngier <maz@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: kvmarm@...ts.linux.dev,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>,
lkft-triage@...ts.linaro.org,
Linux Regressions <regressions@...ts.linux.dev>,
Fuad Tabba <tabba@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Oliver Upton <oliver.upton@...ux.dev>,
James Morse <james.morse@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Suzuki K Poulose <suzuki.poulose@....com>,
Anders Roxell <anders.roxell@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Dan Carpenter <dan.carpenter@...aro.org>,
Ben Copeland <benjamin.copeland@...aro.org>,
Mark Brown <broonie@...nel.org>,
Aishwarya TCV <Aishwarya.TCV@....com>
Subject: Re: kvm-unit-tests hang on Arm FVP with protected mode
On Fri, 05 Sep 2025 13:28:45 +0100,
Naresh Kamboju <naresh.kamboju@...aro.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@...aro.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.
Powered by blists - more mailing lists