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

Sebastian Ene
2025-02-27T19:42:27Z

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 ***

v1 -> this version:

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 (4):
KVM: arm64: Use the static initializer for the vesion lock
KVM: arm64: Move the ffa_to_linux definition to the ffa header
KVM: arm64: Map the hypervisor FF-A buffers on ffa init
KVM: arm64: Release the ownership of the hyp rx buffer to Trustzone

arch/arm64/kvm/hyp/nvhe/ffa.c | 56 +++++++++++++------------------
drivers/firmware/arm_ffa/driver.c | 24 -------------
include/linux/arm_ffa.h | 24 +++++++++++++
3 files changed, 47 insertions(+), 57 deletions(-)

--
2.48.1.711.g2feabab25a-goog