From: Eric Auger <eric.auger@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, miguel.luis@oracle.com,
peter.maydell@linaro.org, richard.henderson@linaro.org,
gkulkarni@amperecomputing.com,
gankulkarni@os.amperecomputing.com
Subject: Re: [PATCH v5 0/5] ARM Nested Virt Support
Date: Tue, 27 May 2025 11:05:06 +0200 [thread overview]
Message-ID: <e3863726-6662-417e-ab7d-005c5ff9af69@redhat.com> (raw)
In-Reply-To: <86msayec3a.wl-maz@kernel.org>
Hi Marc,
On 5/27/25 9:39 AM, Marc Zyngier wrote:
> Hi Eric,
>
> On Tue, 27 May 2025 07:24:32 +0100,
> Eric Auger <eric.auger@redhat.com> wrote:
>> Now that ARM nested virt has landed in kvm/next, let's turn the series
>> into a PATCH series. The linux header update was made against kvm/next.
>>
>> For gaining virt functionality in KVM accelerated L1, The host needs to
>> be booted with "kvm-arm.mode=nested" option and qemu needs to be invoked
>> with: -machine virt,virtualization=on.
> Thanks for respinning this series.
>
> Do you have any plan to support the non-VHE version of the NV support
> (as advertised by KVM_CAP_ARM_EL2_E2H0)? It would allow running lesser
> hypervisors (such as *cough* Xen *cough*), which completely rely on
> HCR_EL2.E2H being 0?
yes I can definitively extend the series to support
KVM_ARM_VCPU_HAS_EL2_E2H0.
Eric
>
>
> Thanks,
>
> M.
>
next prev parent reply other threads:[~2025-05-27 9:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 6:24 [PATCH v5 0/5] ARM Nested Virt Support Eric Auger
2025-05-27 6:24 ` [PATCH v5 1/5] linux-headers: Update against kvm/next Eric Auger
2025-05-27 6:24 ` [PATCH v5 2/5] hw/arm: Allow setting KVM vGIC maintenance IRQ Eric Auger
2025-05-27 6:24 ` [PATCH v5 3/5] target/arm/kvm: Add helper to detect EL2 when using KVM Eric Auger
2025-05-27 6:24 ` [PATCH v5 4/5] target/arm: Enable feature ARM_FEATURE_EL2 if EL2 is supported Eric Auger
2025-05-27 6:24 ` [PATCH v5 5/5] hw/arm/virt: Allow virt extensions with KVM Eric Auger
2025-06-17 14:17 ` Alyssa Ross
2025-06-17 14:52 ` Eric Auger
2025-06-17 15:10 ` Eric Auger
2025-06-17 15:23 ` Miguel Luis
2025-06-17 15:41 ` Eric Auger
2025-06-17 15:50 ` Miguel Luis
2025-06-19 9:40 ` Eric Auger
2025-06-19 13:29 ` Eric Auger
2025-06-19 16:04 ` Alyssa Ross
2025-06-20 16:20 ` Miguel Luis
2025-05-27 7:39 ` [PATCH v5 0/5] ARM Nested Virt Support Marc Zyngier
2025-05-27 9:05 ` Eric Auger [this message]
2025-05-27 11:40 ` Miguel Luis
2025-05-27 12:02 ` Marc Zyngier
2025-05-27 13:24 ` Miguel Luis
2025-05-27 13:46 ` Marc Zyngier
2025-05-27 15:55 ` Miguel Luis
2025-05-27 16:52 ` Marc Zyngier
2025-05-27 23:52 ` Miguel Luis
2025-05-28 8:07 ` Marc Zyngier
2025-06-19 8:19 ` Eric Auger
2025-06-19 8:33 ` Miguel Luis
2025-05-27 11:33 ` Miguel Luis
2025-05-27 12:01 ` Marc Zyngier
2025-05-27 12:54 ` Miguel Luis
2025-05-27 13:11 ` Eric Auger
2025-05-27 14:15 ` 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=e3863726-6662-417e-ab7d-005c5ff9af69@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=gkulkarni@amperecomputing.com \
--cc=maz@kernel.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).