linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: 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>
Cc: Fuad Tabba <tabba@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marc Zyngier <maz@kernel.org>,
	 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: kvm-unit-tests hang on Arm FVP with protected mode
Date: Fri, 5 Sep 2025 17:58:45 +0530	[thread overview]
Message-ID: <CA+G9fYsT3b3Qd-m6tSDOgAXpgLPWz0QD_Z6a+_ff4oTecA85PQ@mail.gmail.com> (raw)

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.

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

Links:
https://regressions.linaro.org/lkft/linux-mainline-master/v6.17-rc4/lava/kvm-unit-tests/history/?page=1
https://qa-reports.linaro.org/api/testruns/29720932/log_file/

--
Linaro LKFT
https://lkft.linaro.org


             reply	other threads:[~2025-09-05 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 12:28 Naresh Kamboju [this message]
2025-09-05 12:42 ` kvm-unit-tests hang on Arm FVP with protected mode Marc Zyngier
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=CA+G9fYsT3b3Qd-m6tSDOgAXpgLPWz0QD_Z6a+_ff4oTecA85PQ@mail.gmail.com \
    --to=naresh.kamboju@linaro.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=maz@kernel.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;
as well as URLs for NNTP newsgroup(s).