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 125473AC0EF; Fri, 4 Sep 2026 07:26:01 +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=1788506763; cv=none; b=fvqM9xGvJZ6Cpk46BH0123/WH+VjEE+d5dc+gY6SSdQ3TLqdqPtLvTZHyXAbVepqkWjn/5UO11G2v//ullWl2fft5BDczTT9Ojv52IoXyyouHjCEyfDyI6teF5t0qiuNCS/ph3IVUMXO8mXVWepkmz4ungU84dpdbO4yUSR1NsI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788506763; c=relaxed/simple; bh=PnAuwQTV5It9jrIlsyrOzsSWHozeqc0I6+KizSVPYrM=; h=Date:Message-ID:From:To:Cc:Subject:In-Reply-To:References: MIME-Version:Content-Type; b=TNVttYuDcX1cbyqTcT0zpsSfOiPnJ5r9eFOZSByxgMGCIbGwGHpdk/R/MezomUaKfIisJIB+15No4JhOgTkWLyNm3IfW16EZVJkfiDRXNYQfYsp5mQKD/qgywSxq6kLP3P4mg8912BBbs52AgiwOFum1SswYVath5noLnOiCh0w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=oxTEmNQt; 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="oxTEmNQt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A4BEE1F00A3D; Fri, 4 Sep 2026 07:26:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1788506761; bh=1CKwJBrd7xoF/6DS3YB+v9BgkGZl8PEjVmi5LuS+nVI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=oxTEmNQtLuGuZ2NmHQN38wOM9DPYvfIau9JROQpQyyH0cZo/PqFJpXZ7jD1kJM1wI +F+OLekrZY+ycG1Amu4lJ2z3MlazmmsCqFm2Fth2qIIxqyPogQ4P/8i70TXjt53xM5 cc8gbg0A8HYEMfFDsVRLAhhGKaENsk5GVNpmWqtgf9KIyLm6LgXi7hxdQN/E5onLrh sDtu76o7MdBqmX5ubQjOvOS53kiSfU1bqkEzI5mJyUdscXig4umdPrFBY78ro2MMx8 3XERDVybB6aqGCJ6AMvuY9q4gdkHLNi7pZnbXSx0R+suaOaMlhkacIsUDUXqmE5BAa cahdpfdj39PiA== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-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 1x2OJD-00000004h5I-1GfT; Fri, 04 Sep 2026 07:25:59 +0000 Date: Fri, 04 Sep 2026 08:25:58 +0100 Message-ID: <86pkyt4gvt.wl-maz@kernel.org> From: Marc Zyngier To: Mark Brown Cc: Oliver Upton , Fuad Tabba , Joey Gouly , Steffen Eiden , Suzuki K Poulose , Zenghui Yu , Catalin Marinas , Will Deacon , Mark Rutland , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] KVM: arm64: Enable S1PIE for nVHE and hVHE In-Reply-To: <20260904-kvm-arm64-nvhe-pie-v1-2-29d59f245e6c@kernel.org> References: <20260904-kvm-arm64-nvhe-pie-v1-0-29d59f245e6c@kernel.org> <20260904-kvm-arm64-nvhe-pie-v1-2-29d59f245e6c@kernel.org> 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: linux-kernel@vger.kernel.org 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: broonie@kernel.org, oupton@kernel.org, fuad.tabba@linux.dev, joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false On Fri, 04 Sep 2026 00:14:42 +0100, Mark Brown wrote: > > When FEAT_S1PIE (stage 1 permission indirection) is supported we > currently enable and use it in the hypervisor when running in VHE mode > but not when running in nVHE or hVHE mode. While systems with > FEAT_S1PIE would normally use VHE users can configure them for nVHE or > hVHE, for example in order to run protected guests. Enable FEAT_S1PIE > with nVHE and hVHE. No. nVHE is dead, and I'm not adding support for random stuff that appeared over 10 years after v8.0. If you have S1PIE, you have VHE. If you force the kernel to run with E2H==0, that's your own problem. M. -- Without deviation from the norm, progress is not possible.