[PATCH v8 0/7] KVM: arm64: Forward FFA_NOTIFICATION* calls to TrustZone

[Will Deacon]

Hi Oliver, Marc,

On Wed, Jul 29, 2026 at 12:13:00PM +0000, Sebastian Ene wrote:
> Remove the FFA_NOTIFICATION* calls from the blocklist used by the pKVM
> FF-A proxy. This restriction was preventing the use of asynchronous
> signaling mechanisms defined by the Arm FF-A specification to
> communicate with the secure services.
> While these calls are markes as optional, there is no reason why the
> hypervisor proxy would block them because:
> 
> 1. Host is the Sole Non-Secure Endpoint: The Host operates as the
>    only Non-Secure VM ID (VM ID 0) recognized by the Secure World.
>    Because all forwarded notifications are inherently attributed to
>    the Host by the SPMC, there is no risk of VM ID spoofing
>    originating from the Normal World.
> 
> 2. No Memory Pointers or Addresses: The FFA_NOTIFICATION_* ABIs
>    operate strictly via register-based parameters, passing only
>    VM IDs, VCPU IDs, flags, and bitmaps. Because these calls do
>    not contain memory addresses, offsets, or pointers, forwarding
>    them doesn't pose a risk of memory-based confused deputy attack
>    (e.g., tricking the SPMC into overwriting protected memory).
> 
> The pKVM proxy behaves as a relayer and it doesn't currently have its
> own FF-A ID(only the host has the ID 0). The behavior of the setup
> flow is covered by the spec in the: '10.9 Notification support without
> a Hypervisor'.
> 
> While at it, enforce the MBZ/SBZ fields defined by the spec to prevent
> odd behavior when a new version starts making use of the reserved
> registers.
> 
> ---
> v8:
> - rebased on 7.2-rc3
> - no other changes

I suspect the mention of FF-A in $SUBJECT might have pushed this off
your priority list, but please could you consider picking these up?

They've all been acked and the code hasn't changed since v7 (posted end
of June). We're not in a huge rush, so 7.4 is fine if you're done for
7.3.

Cheers,

Will