From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 972AA3D4135 for ; Wed, 7 Oct 2026 09:20:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791364883; cv=none; b=LzH0i+Odumc/VqSKIbKSpk3kcLHAYb4kFBvDf34behfV/H3yCP/5lp+ac3alSOjSGtzsqMvZ0ieDDHfmGHn6FOwxenuWZj3FRTghRKaVT8Y7yyGptQ6c0sMIA1vtDPK1l4Cn/KD8N8uRzNpqLmRdnn+MHkn1gj26IMEai8l8pUE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791364883; c=relaxed/simple; bh=opmN9wi4Yy8hW+H8AZW92vjJdGqpEOJ3A8Pa6J3rivA=; h=Date:Message-ID:From:To:Cc:Subject:In-Reply-To:References: MIME-Version:Content-Type; b=GaNtPft7/9W7MFE9hIG3wVjY9kJxsQ7icxnY+AgFmAU8n/Z6T+2bB0hLwkN8trBNWTFAEqjPeyxdywBbxE0Fh3UrgJQwdPpFvgBxIGXUw4zS1IkS3WqH33kXrFnv/aShsxaanPvtBJ+1AJY++rABTNX0EpykOMPjbRSpcUhpr+A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=IS1s6fxw; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="IS1s6fxw" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E0AD11F0089C; Wed, 7 Oct 2026 09:20:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791364816; bh=kVmEn3eqUyM2fWrdbC7yW74tAHSLFoixorcTuIO8mFU=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=IS1s6fxwB2XUZeF1+COiBBg0zOHFiVepZx0iHbVfDioLhejOmfTBOwF6WRCspZ04Z J7wJcPTeFfgL8bBeJVgBnnUEW5eaetO5nAme5UMyz+LYazX/p9WSv4Y3Q1eh8FGPOU 999mYKBSfdBmLrvTCzTtuFr5fBjasW2Z4InZcnRdgcVWMimJDtzi4mtZ+Eo/ANhmF3 vd3C+HOWX8XbVOkwa0DUB0ygSW85tf0heGARgbih+vHvbn6nz77/5x66rWt3Yy1mb1 MCAc4WNPciz+GNLovx06hTFHVB0CT+Pvgt2bWcVmyvPOBa3EuHktFwwCEr6gv7tXyx RITsONJIn3bVw== Received: from sofa.misterjones.org ([185.219.108.64] helo=lobster-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xENos-00000000CUO-2iSC; Wed, 07 Oct 2026 09:20:14 +0000 Date: Wed, 07 Oct 2026 10:23:24 +0100 Message-ID: <877bjt3lv7.wl-maz@kernel.org> From: Marc Zyngier To: Jasmin Mulaosmanovic Cc: "kvmarm@lists.linux.dev" , Sheridan Ethier , Phil Giroux Subject: Re: KVM progress with FEAT_NV2 In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/30.1 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) Precedence: bulk X-Mailing-List: kvmarm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: jmulaosmanovic@qnx.com, kvmarm@lists.linux.dev, sethier@qnx.com, pgiroux@qnx.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Hi Jasmin, On Tue, 06 Oct 2026 20:01:22 +0100, Jasmin Mulaosmanovic 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.