All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Will Deacon <will@kernel.org>,
	Julien Thierry <julien.thierry.kdev@gmail.com>,
	kvm@vger.kernel.org, kvmarm@lists.linux.dev
Subject: Re: [PATCH kvmtool 0/3] arm64: Nested virtualization support
Date: Fri, 20 Jun 2025 12:13:12 +0100	[thread overview]
Message-ID: <86ikkqd5tj.wl-maz@kernel.org> (raw)
In-Reply-To: <20250620104454.1384132-1-andre.przywara@arm.com>

Hi Andre,

On Fri, 20 Jun 2025 11:44:51 +0100,
Andre Przywara <andre.przywara@arm.com> wrote:
> 
> Thanks to the imperturbable efforts from Marc, arm64 support for nested
> virtualization has now reached the mainline kernel, which means the
> respective kvmtool support should now be ready as well.

Thanks for pushing this stuff out.

> 
> Patch 1 updates the kernel headers, to get the new EL2 capability, and
> the VGIC device control to setup the maintenance IRQ.
> Patch 2 introduces the new "--nested" command line option, to let the
> VCPUs start in EL2. To allow KVM guests running in such a guest, we also
> need VGIC support, which patch 3 allows by setting the maintenance IRQ.
> 
> Tested on the FVP (with some good deal of patience), and some commercial
> (non-fruity) hardware, down to a guest's guest's guest.
> 
> Cheers,
> Andre
> 
> P.S.: Marc: I saw the other patches in your kernel.org repo, do we need any
> of them - HYP timer IRQ, E2H0, counter offset?

Yes, please. They are very much necessary, and should serve as a
template for other VMMs (exposing all the interrupts is required, the
counter offset is necessary to test things resembling live migration,
and the e2h0 selection to run nVHE.

You can probably ignore the virtio patch for now, as this needs to be
properly debugged,

> I guess E2H0 for fruity hardware, what about the others?

The other way around. The '--e2h0' option forces the use of
HCR_EL2.NV1. Rotten fruits can't use NV1 (they actually can, but the
EL2 S1 PTW is fscked, so we hide it from KVM). However, other
implementations do have proper NV1 support, and that option is
extremely useful to boot a nVHE hypervisor.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

      parent reply	other threads:[~2025-06-20 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 10:44 [PATCH kvmtool 0/3] arm64: Nested virtualization support Andre Przywara
2025-06-20 10:44 ` [PATCH kvmtool 1/3] Sync kernel UAPI headers with v6.16-rc1 Andre Przywara
2025-06-20 10:44 ` [PATCH kvmtool 2/3] arm64: Initial nested virt support Andre Przywara
2025-06-20 11:09   ` Alexandru Elisei
2025-06-20 11:52     ` Marc Zyngier
2025-06-20 13:43       ` Alexandru Elisei
2025-06-20 10:44 ` [PATCH kvmtool 3/3] arm64: nested: add support for setting maintenance IRQ Andre Przywara
2025-06-20 11:13 ` 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=86ikkqd5tj.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.