From: Marc Zyngier <maz@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, miguel.luis@oracle.com, haibo.xu@linaro.org,
richard.henderson@linaro.org, gkulkarni@amperecomputing.com
Subject: Re: [RFC v2 0/5] ARM Nested Virt Support
Date: Mon, 12 Feb 2024 17:18:41 +0000 [thread overview]
Message-ID: <d9da1d0ab970be3471187224241f3cee@kernel.org> (raw)
In-Reply-To: <CAFEAcA_SFtmCCFBPwWjJF3uygdpdqoZuYLaQQP186fyQ+dJEHA@mail.gmail.com>
On 2024-02-09 18:57, Peter Maydell wrote:
> On Fri, 9 Feb 2024 at 16:00, Eric Auger <eric.auger@redhat.com> wrote:
>>
>> This series adds ARM Nested Virtualization support in KVM mode.
>> This is a respin of previous contributions from Miguel [1] and Haibo
>> [2].
>>
>> This was tested with Marc's v11 [3] on Ampere HW with fedora L1 guest
>> and
>> L2 guests booted without EDK2. However it does not work yet with
>> EDK2 but it looks unrelated to this qemu integration (host hard
>> lockups).
>>
>> The host needs to be booted with "kvm-arm.mode=nested" option and
>> qemu needs to be invoked with :
>>
>> -machine virt,virtualization=on
>>
>> There is a known issue with hosts supporting SVE. Kernel does not
>> support both
>> SVE and NV2 and the current qemu integration has an issue with the
>> scratch_host_vcpu startup because both are enabled if exposed by the
>> kernel.
>> This is independent on whether sve is disabled on the command line.
>> Unfortunately
>> I lost access to the HW that expose that issue so I couldn't fix it in
>> this
>> version.
>
> You can probably repro that by running the whole setup under
> QEMU's FEAT_NV emulation, which will be able to give you a CPU
> with both FEAT_NV and SVE.
>
> Personally I think that this is a kernel missing-feature that
> should really be fixed as part of getting the kernel patches
> upstreamed. There's no cause to force every userspace VMM to
> develop extra complications for this.
I don't plan to make NV visible to userspace before this is fixed.
Which may delay KVM NV by another year or five, but I don't think
anyone is really waiting for it anyway.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2024-02-12 17:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 15:59 [RFC v2 0/5] ARM Nested Virt Support Eric Auger
2024-02-09 15:59 ` [RFC v2 1/5] [Placeholder] headers: Partial headers update for NV2 enablement Eric Auger
2024-02-09 15:59 ` [RFC v2 2/5] hw/arm: Allow setting KVM vGIC maintenance IRQ Eric Auger
2024-03-05 16:46 ` Peter Maydell
2024-03-25 17:50 ` Eric Auger
2024-03-26 11:04 ` Eric Auger
2024-02-09 15:59 ` [RFC v2 3/5] target/arm/kvm: Add helper to detect EL2 when using KVM Eric Auger
2024-02-09 18:54 ` Philippe Mathieu-Daudé
2024-02-09 15:59 ` [RFC v2 4/5] target/arm: Enable feature ARM_FEATURE_EL2 if EL2 is supported Eric Auger
2024-03-05 16:49 ` Peter Maydell
2024-03-25 18:42 ` Eric Auger
2024-02-09 15:59 ` [RFC v2 5/5] hw/arm/virt: Allow virt extensions with KVM Eric Auger
2024-02-09 18:57 ` [RFC v2 0/5] ARM Nested Virt Support Peter Maydell
2024-02-12 17:15 ` Eric Auger
2024-02-12 17:18 ` Marc Zyngier [this message]
2024-03-05 16:57 ` Peter Maydell
2024-03-26 10:09 ` Eric Auger
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=d9da1d0ab970be3471187224241f3cee@kernel.org \
--to=maz@kernel.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=gkulkarni@amperecomputing.com \
--cc=haibo.xu@linaro.org \
--cc=miguel.luis@oracle.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).