All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Jasmin Mulaosmanovic <jmulaosmanovic@qnx.com>
Cc: "kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
	Sheridan Ethier <sethier@qnx.com>, Phil Giroux <pgiroux@qnx.com>
Subject: Re: KVM progress with FEAT_NV2
Date: Wed, 07 Oct 2026 10:23:24 +0100	[thread overview]
Message-ID: <877bjt3lv7.wl-maz@kernel.org> (raw)
In-Reply-To: <YT6PR01MB10847DF9576E4055F3F8F95F3C0952@YT6PR01MB10847.CANPRD01.PROD.OUTLOOK.COM>

Hi Jasmin,

On Tue, 06 Oct 2026 20:01:22 +0100,
Jasmin Mulaosmanovic <jmulaosmanovic@qnx.com> wrote:
> 
> Hi Marc,
> 
> I'm a product manager at QNX looking at the status of nested
> virtualization support in KVM. The ARM team pointed me to you as the
> right person to contact.
>
> Our automotive customers run QNX-based systems in the cloud. We want
> to run multiple QNX Hypervisor instances on top of KVM, with each
> instance hosting its own Android and Linux guests.
> 
> We understand there has been ongoing upstream work on FEAT_NV2
> support. Is there a roadmap or expected timeline for KVM to support
> this configuration with hardware acceleration?

Support for FEAT_NV2 has been merged about a year ago (in 6.17, if I
remember correctly), as an experimental feature, and is regularly
improved. There is also some limited support in upstream QEMU and
kvmtool to drive this.

As for a roadmap, we don't have one. Architectural features are
enabled as needed, and as people find the time (and interest) to
support them. Whether the existing KVM support matches what QNX
requires, I can't tell.

Hope this helps,

	M.

-- 
Jazz isn't dead. It just smells funny.

           reply	other threads:[~2026-10-07  9:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <YT6PR01MB10847DF9576E4055F3F8F95F3C0952@YT6PR01MB10847.CANPRD01.PROD.OUTLOOK.COM>]

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=877bjt3lv7.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=jmulaosmanovic@qnx.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=pgiroux@qnx.com \
    --cc=sethier@qnx.com \
    /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.