From: Oliver Upton <oliver.upton@linux.dev>
To: Jan Kotas <jank@cadence.com>
Cc: Marc Zyngier <maz@kernel.org>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Subject: Re: KVM NV + SVE host OS warning
Date: Tue, 7 Oct 2025 16:26:14 -0700 [thread overview]
Message-ID: <aOWhlvC1kROWfMSv@linux.dev> (raw)
In-Reply-To: <25C5E00D-62BC-4188-8642-21913446B32C@global.cadence.com>
On Tue, Oct 07, 2025 at 11:12:31AM +0000, Jan Kotas wrote:
> Hello,
>
> I was finally able to do some validation, sorry for a long delay.
No worries, thanks for testing.
> First I applied the "Don't advance PC" patch on top of 6.16.9.
> It fixed the error message, but the Guest didn’t boot.
> I didn’t debug it further.
>
> Then I applied it on top of 6.17 along with Oliver’s second patch.
> Guest OS stops booting because of an exception, when accessing ZCR_EL2.
>
> I checked the ESR_EL2 register and it has 0x66000000:
>
> Access to SVE functionality trapped as a result of CPACR_EL1.ZEN,
> CPTR_EL2.ZEN, CPTR_EL2.TZ, or CPTR_EL3.EZ
>
> I’ll continue the debug to make sure the issue is not on our end.
Could you please share the repro steps? Also, is the guest kernel
unmodified? FWIW, I tested kvmarm/next as the kernel at all levels,
kvmtool as the VMM and E2H=RES1.
While the trap to L0 is unavoidable, reinjecting the SVE trap depends on
the L0 view of CPTR_EL2 which originates from the in-memory value.
Unless there's a bug lurking this should always be in agreement with the
effective value programmed in CPACR_EL1.
Thanks,
Oliver
next prev parent reply other threads:[~2025-10-07 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <799DD5E5-8BC2-47B3-A919-33429D3FB2F1@global.cadence.com>
2025-09-25 14:38 ` KVM NV + SVE host OS warning Marc Zyngier
2025-09-25 15:10 ` Jan Kotas
2025-09-25 15:35 ` Marc Zyngier
2025-09-25 22:46 ` Oliver Upton
2025-10-07 11:12 ` Jan Kotas
2025-10-07 23:26 ` Oliver Upton [this message]
2025-10-08 6:32 ` Jan Kotas
2025-10-08 7:29 ` Jan Kotas
2025-10-08 9:28 ` Marc Zyngier
2025-10-08 9:45 ` Jan Kotas
2025-10-08 11:58 ` Marc Zyngier
2025-10-08 13:43 ` Jan Kotas
2025-10-08 15:22 ` Marc Zyngier
2025-10-09 10:59 ` Jan Kotas
2025-10-09 12:22 ` Marc Zyngier
2025-10-09 14:41 ` Jan Kotas
2025-10-09 15:01 ` Marc Zyngier
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=aOWhlvC1kROWfMSv@linux.dev \
--to=oliver.upton@linux.dev \
--cc=jank@cadence.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@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