From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 4B9081CEEB2; Wed, 30 Jul 2025 21:15:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753910117; cv=none; b=SY8GYLo90aTVunQJY2jc1c+ZVrN45vZSwfQimKY8Vthx1vsFO/iyqJxkWv5fmmXbNKeZYTGLLeS4jC49aL0r4gQhir+9a97AuzpP0KhyyZdi95cHdjzme/cjSxjoAZgYOeIrM5bA6RS9CE0OjdCtt94sybRgJ1V4OtX4EVoaMow= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1753910117; c=relaxed/simple; bh=2n4ZpBiH49X1Xk87/93II76uvYGcP9XBMVe0ouEKtOg=; h=From:Subject:Date:Message-Id:MIME-Version:Content-Type:To:Cc; b=rV8gy3JCiVg5ygxfRGzNcV4wvzeMX/S2lweyUK/ss51jTtvYtZ2VujMhBuQ0nCohf0Htbiwx2J/r6o87gsePU7ohKkyCHAWHPmrDLy7GRij5EsYfDP+CI8dfiJzH/Li1ax4qkjhlaNhMbY0lcIUpsrfv5Nle2ypEEltnsZdsHPU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JXCN3G7J; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="JXCN3G7J" Received: by smtp.kernel.org (Postfix) with ESMTPS id C9BD3C4CEF7; Wed, 30 Jul 2025 21:15:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1753910116; bh=2n4ZpBiH49X1Xk87/93II76uvYGcP9XBMVe0ouEKtOg=; h=From:Subject:Date:To:Cc:Reply-To:From; b=JXCN3G7Jg9t3UnLMLZGyHyFRyt8B6Zk69b7/uUscRYJ4rbUWGN2Uit38kphaxjIh4 ZXHXLcIo47UhbOOfJKlNiM8Jy/C54O8iXSghMzbKTJgIqaiJlCl7C7VU8fYvoKrSoR 4YlJ1si6iTjV5PmCDzTyBKTs9nhY+RK0oTFcubkL5U2tlrVqLH8sUAi8s1Ufnz8USt uRHAMiFrnnNgsXZaRxtQXSdsQhuax4z25+qavcKn/eDdw8CnPt/8zoDePU7xRj/nr7 Yx4jCR9uYTx7v4fyRM3Jus23EGTeE6r1Z7DItkzh+Syv+wYrpBSL/TOCqL3FvDfvTz 2BiE7wehw9J1A== Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id B45BFC87FC9; Wed, 30 Jul 2025 21:15:16 +0000 (UTC) From: Per Larsen via B4 Relay Subject: [PATCH v9 0/6] KVM: arm64: Support FF-A 1.2 Date: Wed, 30 Jul 2025 21:15:03 +0000 Message-Id: <20250730-virtio-msg-ffa-v9-0-7f1b55c8d149@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-B4-Tracking: v=1; b=H4sIAFeLimgC/23QTWrDMBCG4asEr6sgjf7GXeUepQtFGjmC2Aqya 1pC7l4lUOJWXc7i+XiZazdTSTR3r7trV2hNc8pTPfqXXedPbhqIpVDvDjhorrlhaypLymycBxa jYwAuWvA9CM27ii6FYvp8DL691zuWPLLlVMhtZ4BXwHEvAZRUggl2oXI+pHH8mNy07H0e72OnN C+5fD3iVrhP/gzg344VGGcUUEXkWvZGH4achzM9pu4hq9x4IRsvqw/GeGtiFEfwjVdb3/xhVdV r5ESWU+0TjddPb0TfeF29EvWTqDUit403Gw+28aZ69Bxi6BUF1/bbp7dcNN5W3/faRS+DRE2Nx 43/px+r55KQMBwJtfnlb7fbNwsKd2tqAgAA X-Change-ID: 20250506-virtio-msg-ffa-22af72c92150 To: Marc Zyngier , Oliver Upton , Joey Gouly , Suzuki K Poulose , Zenghui Yu , Catalin Marinas , Will Deacon , Sudeep Holla Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org, ahomescu@google.com, armellel@google.com, arve@android.com, ayrton@google.com, qperret@google.com, sebastianene@google.com, qwandor@google.com, Per Larsen X-Mailer: b4 0.14.2 X-Developer-Signature: v=1; a=ed25519-sha256; t=1753910116; l=5745; i=perlarsen@google.com; s=20250508; h=from:subject:message-id; bh=2n4ZpBiH49X1Xk87/93II76uvYGcP9XBMVe0ouEKtOg=; b=+DOO1WEnCkFBiHOS5vVKPUiJukyaqHM8vlRr0fjnUe6IV7jLM6XtelOqmk+9SG/xKV6JtXFQ1 u/erbE1x3QBCoxuSf9xZ5eAn+Z/qoCIyj5z9j1UPbs6ShRHUhmmZxn+ X-Developer-Key: i=perlarsen@google.com; a=ed25519; pk=jjc/Ta4VmrLRmMoahP6d1mBcKzvWU+nsmdtYe2oS2kQ= X-Endpoint-Received: by B4 Relay for perlarsen@google.com/20250508 with auth_id=402 X-Original-From: Per Larsen Reply-To: perlarsen@google.com Hi, The FF-A 1.2 specification introduces a new SEND_DIRECT2 ABI which allows registers x4-x17 to be used for the message payload. This patch set prevents the host from using a lower FF-A version than what has already been negotiated with the hypervisor. This is necessary because the hypervisor does not have the necessary compatibility paths to translate from the hypervisor FF-A version to a previous version. Support for FF-A 1.2 in the hypervisor is added as a precursor to the addition of the FFA_MSG_SEND_DIRECT_REQ2 messaging interface. Notably, this patch updates all smc calls to use SMCCC 1.2 as it makes it simpler to support interfaces that need to accept more than 8 arguments and/or return more than 4 values. The list of optional/unsupported interfaces was updated to reflect additions in FF-A 1.2. Tested by booting Android under QEMU and loading Trusty as the guest VM and observing the SEND_DIRECT2 ABI being used successfully during guest boot. Changes in v9: - 2/7 -> 2/6: Updated explanatory comment in ffa_set_retval - 4/7 -> 4/6: Restore to v7: Mark FFA_MSG_SEND_DIRECT_REQ2 unsupported - 5/7 -> 5/6: Added Acked-by: Will Deacon - 6/7 -> 6/6: Added Acked-by: Will Deacon - 7/7: Dropped - Link to v8: https://lore.kernel.org/r/20250719-virtio-msg-ffa-v8-0-03e8e8dbe856@google.com Changes in v8: - 2/5 -> 2/7: Use func_id argument to distinguish SMC32/SMC64. Update rationale. - 4/5 -> 4/7: Split up 4/5: Add optional FF-A 1.2 interfaces - 4/5 -> 5/7: Split up 4/5: Mask FFA_RXTX_MAP minium buffer size in a2. Don't check MBZ bits. - 4/5 -> 6/7: Remainder of 4/5: Bump supported version to FF-A 1.2 - 5/5 -> 7/7: Don't check src id in do_ffa_direct_msg2 - Link to v7: https://lore.kernel.org/r/20250701-virtio-msg-ffa-v7-0-995afc3d385e@google.com Changes in v7: - 0/6: Revised cover letter slightly - 4/6: ffa_call_supported: Clarify optional interfaces hyp_ffa_post_init: Sanitize MBZ bits in x2 and x3 address nit: use GENMASK - Link to v6: https://lore.kernel.org/r/20250627-virtio-msg-ffa-v6-0-8c02fd94edac@google.com Changes since v5: - 3/6 -> 2/5: Merged with parent patch as they were closely related Don't rename variables from "res" to "regs" to avoid churn Update and clarify reasoning for condition added to ffa_set_retval Adopt style suggested by Marc when passing regs to arm_smccc_1_2_smc Fix inadvertent duplicate statements in ffa_{map,unmap}_hyp_buffers - Link to v5: https://lore.kernel.org/r/20250619-virtio-msg-ffa-v5-0-412c98558807@google.com Changes since v4: - 1/5 -> 1/6: Added Acked-by: Will Deacon y Reworded patch subject and description - 2/5: Dropped patch: zero x4-x7 in ffa_set_retval - 2/6: New: use SMCCC 1.2 during hyp init - 3/6: New: use SMCCC 1.2 in host FF-A handler - 3/5 -> 4/6: No change; can revisit denylist design in later patchset Added Acked-by: Will Deacon - 4/5 -> 5/6: No change - 5/5 -> 6/6: No change - Link to v4: https://lore.kernel.org/r/20250516-virtio-msg-ffa-v4-0-580ee70e5081@google.com Changes since v3: - all: Remove Signed-off-by: Per Larsen - 2/5: Split out from 2/3, zero x4-x7 in set_ffa_retval - 3/5: Split out from 2/3, Mark FFA_NOTIFICATION_* calls as unsupported - 2/3 -> 4/5: Drop ffa_get_hypervisor_version, access hyp_ffa_version directly when version negotiation is complete. - 3/3 -> 5/5: Call ffa_to_smccc_1_2_error directly in do_do_ffa_direct_msg2 Push call to ffa_call_needs_smccc_1_2 lower down by adding ffa_get_func_id and ffa_set_retval_smccc_1_x. Drop ffa_to_smccc_1_2_regs and ffa_to_smccc_1_2_regs_prop as they are no longer used. - Link to v3: https://lore.kernel.org/r/20250513-virtio-msg-ffa-v3-0-d66c76ff1b2c@google.com Changes since v2: - 2/3: Removed files added by mistake. Add and use ffa_get_hypervisor_version to access hyp_ffa_version - 3/3: Use ffa_get_hypervisor_version to access hyp_ffa_version safely - Link to v2: https://lore.kernel.org/r/20250508-virtio-msg-ffa-v2-0-ed84f8053965@google.com Changes since v1: - 1/3: Simplify commit message; drop long comment in do_ffa_version - 2/3: Correct use of Co-developed-by: footer s/arm_smccc_1_2_smc_fallback/arm_smccc_1_x_smc/ Always access hyp_ffa_version w/lock held Remove superfluous comments in ffa_call_supported Add and use FFA_FEAT_RXTX_MIN_SZ_MASK instead of constant Add FFA_PARTITION_INFO_GET_REGS to calls that require SMCCC 1.2 - 3/3: Always access hyp_ffa_version w/lock held Correct formatting Thanks, Per Larsen -- 2.49.0 --- Per Larsen (6): KVM: arm64: Correct return value on host version downgrade attempt KVM: arm64: Use SMCCC 1.2 for FF-A initialization and in host handler KVM: arm64: Mark FFA_NOTIFICATION_* calls as unsupported KVM: arm64: Mark optional FF-A 1.2 interfaces as unsupported KVM: arm64: Mask response to FFA_FEATURE call KVM: arm64: Bump the supported version of FF-A to 1.2 arch/arm64/kvm/hyp/nvhe/Makefile | 1 + arch/arm64/kvm/hyp/nvhe/ffa.c | 215 ++++++++++++++++++++++++++------------- include/linux/arm_ffa.h | 1 + 3 files changed, 144 insertions(+), 73 deletions(-) --- base-commit: 4b290aae788e06561754b28c6842e4080957d3f7 change-id: 20250506-virtio-msg-ffa-22af72c92150 Best regards, -- Per Larsen