From: Marc Zyngier <maz@kernel.org>
To: Jan Kotas <jank@cadence.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Subject: Re: KVM NV + SVE host OS warning
Date: Thu, 09 Oct 2025 16:01:01 +0100 [thread overview]
Message-ID: <86plawxgpe.wl-maz@kernel.org> (raw)
In-Reply-To: <1BD0A29B-E20A-4BA9-A916-8B975813503C@global.cadence.com>
On Thu, 09 Oct 2025 15:41:28 +0100,
Jan Kotas <jank@cadence.com> wrote:
>
> > On 9 Oct 2025, at 14:22, Marc Zyngier <maz@kernel.org> wrote:
> >
> > As an alternative, and in an effort to keep at least VHE guests
> > running on V2 (and other machines suffering from the same situation),
> > I have posted a potential workaround at [1] for the guest to reliably
> > detect the situation.
> >
> > Could you please test it with your setup and report whether this
> > allows you to boot a VHE guest? You will need to patch the guest.
> >
> > Note that this still won't let you recursively virtualise EL2 (the HW
> > can do it, but KVM in the guest doesn't know it), but that's better
> > than nothing.
>
> Thanks Marc,
> I tried it in my Guest, on top of 6.17.0. It seems to be working.
>
>
> Without HAS_EL2_E2H0:
> CPU features: detected: Virtualization Host Extensions
> CPU: All CPU(s) started at EL2
> kvm [1]: VHE mode initialized successfully
>
>
> With HAS_EL2_E2H0:
> CPU: All CPU(s) started at EL2
> kvm [1]: Hyp nVHE mode initialized successfully
>
> In both cases SVE is also initialized properly.
Great. Would you mind replying to the patch with a Tested-by: tag?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2025-10-09 15:01 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
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 [this message]
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=86plawxgpe.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jank@cadence.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
/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