Merge branch kvm-arm64/ffa-7.4 into kvmarm-master/next

* kvm-arm64/ffa-7.4:
  : \
  : Series allowing FFA notification calls from the host to the secure
  : side, courtesy of Sebastian Ene. From the cover letter:
  :
  : "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)."
  : /
  KVM: arm64: Enforce strict SBZ checks in the FF-A proxy
  KVM: arm64: Support FFA_NOTIFICATION_INFO_GET in host handler
  KVM: arm64: Support FFA_NOTIFICATION_GET in host handler
  KVM: arm64: Support FFA_NOTIFICATION_SET in host handler
  KVM: arm64: Support FFA_NOTIFICATION_UNBIND in host handler
  KVM: arm64: Support FFA_NOTIFICATION_BIND in host handler
  KVM: arm64: Forward FFA_NOTIFICATION_BITMAP calls to Trustzone

Signed-off-by: Marc Zyngier <maz@kernel.org>

0 files changed, 0 insertions, 0 deletions