From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4EADECCD1A5 for ; Tue, 21 Oct 2025 07:50:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: References:In-Reply-To:Subject:Cc:To:From:Message-ID:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=wjsaVsPMd/i3M2GLEMTZ12Tx4fJiPCTF6sF2Z8boweM=; b=N6XfvPDlzLFyeFUvn/WfWTrYuX VH8kIc4/FC63xvzOLqkpKmUuGT2YcOPvdD6LKW0ZhSxw6XzhrCQjbOrWCVUn+nIv2j57FbFDoANBa WJ4XON3oEl2dbqRKUllp/VwMMVCmQLA3pjPRnBVutmPItGARXtcQlDyI8Er9CTw8owxF9YtLiA57C 8Cdkws5WHpAUb5it930jdofKLEqKfCLR/kEze0ZXz0uq5eBdghHoELvtmtM0H2TXFKHgFPZ5Ii9gB 4wl1/lEj+VfTOgo+nx99s6RUdUU/8B5R2wzGopdOIRS6mKV12X/BuVnr1fL2rZYUu9hVPSvxNZT0p i8ik39Wg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vB78W-0000000GAFY-2Yif; Tue, 21 Oct 2025 07:50:28 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vB78U-0000000GADr-0Z2r for linux-arm-kernel@lists.infradead.org; Tue, 21 Oct 2025 07:50:27 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id BD4374588A; Tue, 21 Oct 2025 07:50:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 99228C4CEF7; Tue, 21 Oct 2025 07:50:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1761033025; bh=wcjQXdXyz4a64xPChG6OrBbIDGawzNQC7URHkyMcw9s=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=mKp8C6KkuWJAne+5zLlmaPxKLDRxc161Dmorh/7VwBWhIa4rOhvF+9t5O7TfUkGVN 5J8AZxqfUW3IoY6cvJCxl3akQySI1hE1HTLiqI81hBekdUbevEBVf6wMOpBFCvC4RB fJK80tE4UebXUiYLIb86fa5viFBux7BXSb+APfw2aW6K7hirWZAP5kC5kJQUaDbXEf D3+4ubqnMq76+F5kSiWBuuYzKPsHyGvQM5K+bhGM0B6h9NJq29ui1zi8Kz/6un/Y+W egkYBE9PEBsU0dQDzK+pfmBvipreHtG5jeD0a3d90cYvS/ZpzijvYK7WapUUBhC3kQ wVKrkvEKqxnYA== 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 1vB78R-0000000FkvS-0gGO; Tue, 21 Oct 2025 07:50:23 +0000 Date: Tue, 21 Oct 2025 08:50:22 +0100 Message-ID: <86frbcwv5t.wl-maz@kernel.org> From: Marc Zyngier To: Mark Brown Cc: Sascha Bischoff , "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.linux.dev" , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , nd , "oliver.upton@linux.dev" , Joey Gouly , Suzuki Poulose , "yuzenghui@huawei.com" , Paolo Bonzini , Linus Torvalds , Aishwarya.TCV@arm.com Subject: Re: [PATCH] KVM: arm64: gic-v3: Only set ICH_HCR traps for v2-on-v3 or v3 guests In-Reply-To: <23072856-6b8c-41e2-93d1-ea8a240a7079@sirena.org.uk> References: <20251007160704.1673584-1-sascha.bischoff@arm.com> <23072856-6b8c-41e2-93d1-ea8a240a7079@sirena.org.uk> 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) 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, Sascha.Bischoff@arm.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, nd@arm.com, oliver.upton@linux.dev, Joey.Gouly@arm.com, Suzuki.Poulose@arm.com, yuzenghui@huawei.com, pbonzini@redhat.com, torvalds@linux-foundation.org, Aishwarya.TCV@arm.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20251021_005026_232477_DE74A9E4 X-CRM114-Status: GOOD ( 28.90 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 21 Oct 2025 01:21:56 +0100, Mark Brown wrote: > > On Tue, Oct 07, 2025 at 04:07:13PM +0000, Sascha Bischoff wrote: > > The ICH_HCR_EL2 traps are used when running on GICv3 hardware, or when > > running a GICv3-based guest using FEAT_GCIE_LEGACY on GICv5 > > hardware. When running a GICv2 guest on GICv3 hardware the traps are > > used to ensure that the guest never sees any part of GICv3 (only GICv2 > > is visible to the guest), and when running a GICv3 guest they are used > > to trap in specific scenarios. They are not applicable for a > > GICv2-native guest, and won't be applicable for a(n upcoming) GICv5 > > guest. > > v6.18-rc2 introduces a failure in the KVM no-vgic-v3 selftest on what > appears to be all arm64 platforms with a GICv3 in all of VHE, nVHE and > pKVM modes: > > # selftests: kvm: no-vgic-v3 > # Random seed: 0x6b8b4567 > # ==== Test Assertion Failure ==== > # arm64/no-vgic-v3.c:66: handled > # pid=3469 tid=3469 errno=4 - Interrupted system call > # 1 0x0000000000402ff7: test_run_vcpu at no-vgic-v3.c:128 > # 2 0x0000000000402213: test_guest_no_gicv3 at no-vgic-v3.c:155 > # 3 (inlined by) main at no-vgic-v3.c:174 > # 4 0x0000ffff7fca7543: ?? ??:0 > # 5 0x0000ffff7fca7617: ?? ??:0 > # 6 0x00000000004023af: _start at ??:? > # ICC_PMR_EL1 no read trap > not ok 25 selftests: kvm: no-vgic-v3 # exit=254 > > introduced by this patch, which is commit 3193287ddffb and which never > appeared in -next prior to being merged into mainline. > > It didn't appear in -next since the arm64 KVM fixes tree is not directly > in -next and it was only pulled into Paolo's tree on Saturday, a few > hours before Paolo sent his pull request to Linus, so there was no > opportunity for it to be picked up. As I've previously suggested it > does seem like it would be a good idea to include the fixes branches for > the KVM arch trees in -next (s390 is there, but I don't see the others), As I explained to you more than once, the answer is still no. We keep the two branches separate for good reasons -- for a start, they are manager by different people. If you want to manage a -fixes tree, go for it. If you want to take the -fixes branch in your CI, I have no objection. Do I support this? Absolutely not. M. -- Without deviation from the norm, progress is not possible.