From: Will Deacon <will@kernel.org>
To: perlarsen@google.com
Cc: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
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
Subject: Re: [PATCH v9 4/6] KVM: arm64: Mark optional FF-A 1.2 interfaces as unsupported
Date: Fri, 8 Aug 2025 13:41:14 +0100 [thread overview]
Message-ID: <aJXwan8iMtRBkiPX@willie-the-truck> (raw)
In-Reply-To: <20250730-virtio-msg-ffa-v9-4-7f1b55c8d149@google.com>
On Wed, Jul 30, 2025 at 09:15:07PM +0000, Per Larsen via B4 Relay wrote:
> From: Per Larsen <perlarsen@google.com>
>
> Mark FF-A 1.2 interfaces as unsupported lest they get proxied. Also mark
> FFA_EL3_INTR_HANDLE as unsupported as it is only valid for physical
> instances.
>
> Signed-off-by: Per Larsen <perlarsen@google.com>
> ---
> arch/arm64/kvm/hyp/nvhe/ffa.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
> index 48183fa78014e420372c4fb5e489519bc652bf53..7fe96fe626d630a9009551e8dec1683617acafbd 100644
> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
> @@ -674,6 +674,13 @@ static bool ffa_call_supported(u64 func_id)
> case FFA_NOTIFICATION_SET:
> case FFA_NOTIFICATION_GET:
> case FFA_NOTIFICATION_INFO_GET:
> + /* Optional interfaces added in FF-A 1.2 */
> + case FFA_MSG_SEND_DIRECT_REQ2: /* Optional per 7.5.1 */
> + case FFA_MSG_SEND_DIRECT_RESP2: /* Optional per 7.5.1 */
> + case FFA_CONSOLE_LOG: /* Optional per 13.1: not in Table 13.1 */
> + case FFA_PARTITION_INFO_GET_REGS: /* Optional for virtual instances per 13.1 */
> + /* Unsupported interfaces added in FF-A 1.2 */
> + case FFA_EL3_INTR_HANDLE: /* Only valid for secure physical instances */
Shouldn't the secure side be rejecting that one for us, then?
> return false;
> }
Regardless,
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2025-08-08 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 21:15 [PATCH v9 0/6] KVM: arm64: Support FF-A 1.2 Per Larsen via B4 Relay
2025-07-30 21:15 ` [PATCH v9 1/6] KVM: arm64: Correct return value on host version downgrade attempt Per Larsen via B4 Relay
2025-07-30 21:15 ` [PATCH v9 2/6] KVM: arm64: Use SMCCC 1.2 for FF-A initialization and in host handler Per Larsen via B4 Relay
2025-08-08 12:39 ` Will Deacon
2025-07-30 21:15 ` [PATCH v9 3/6] KVM: arm64: Mark FFA_NOTIFICATION_* calls as unsupported Per Larsen via B4 Relay
2025-07-30 21:15 ` [PATCH v9 4/6] KVM: arm64: Mark optional FF-A 1.2 interfaces " Per Larsen via B4 Relay
2025-08-08 12:41 ` Will Deacon [this message]
2025-07-30 21:15 ` [PATCH v9 5/6] KVM: arm64: Mask response to FFA_FEATURE call Per Larsen via B4 Relay
2025-07-30 21:15 ` [PATCH v9 6/6] KVM: arm64: Bump the supported version of FF-A to 1.2 Per Larsen via B4 Relay
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=aJXwan8iMtRBkiPX@willie-the-truck \
--to=will@kernel.org \
--cc=ahomescu@google.com \
--cc=armellel@google.com \
--cc=arve@android.com \
--cc=ayrton@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=perlarsen@google.com \
--cc=qperret@google.com \
--cc=qwandor@google.com \
--cc=sebastianene@google.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox