[PATCH v4 0/3] KVM: arm64: Separate the hyp FF-A buffers init from the host

Sebastian Ene
2025-03-26T11:39:06Z

Hello,

This moves the initialization of the hypervisor FF-A buffers
away from the host FF-A map calling path. If the hypervisor
cannot map the buffers with Trustzone, it rejects any FF-A call
when it runs under protected mode.
Other than that it moves the definitions of the ffa_to_linux_err
map from the arm_ffa driver to the ffa header so that the hyp code
can make use of it.

*** Changelog ***

v3 -> this version:

- moved the definition of PARTITION_INFO_GET_RETURN_COUNT_ONLY from
the driver code to the arm_ffa header and dropped the definition
from the last patch.

v2 -> v3:

- dropped the "Map the hypervisor FF-A buffers on ffa init" patch
- added ack & reviewed-by tags
- don't release the ownership of the RX buffer if the flag from
FFA_GET_PARTITION is (1)

v1 -> v2:

Split the patch that maps the ff-a buffers of ffa init and introduce
"Move the ffa_to_linux definition to the ffa header".

Thanks,

Sebastian Ene (3):
KVM: arm64: Use the static initializer for the version lock
firmware: arm_ffa: Move the ffa_to_linux definition to the ffa header
KVM: arm64: Release the ownership of the hyp rx buffer to Trustzone

arch/arm64/kvm/hyp/nvhe/ffa.c | 12 +++++++-----
drivers/firmware/arm_ffa/driver.c | 26 --------------------------
include/linux/arm_ffa.h | 27 +++++++++++++++++++++++++++
3 files changed, 34 insertions(+), 31 deletions(-)

--
2.49.0.395.g12beb8f557-goog