[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250318162510.3280359-1-sebastianene@google.com>
Date: Tue, 18 Mar 2025 16:25:07 +0000
From: Sebastian Ene <sebastianene@...gle.com>
To: catalin.marinas@....com, joey.gouly@....com, maz@...nel.org,
oliver.upton@...ux.dev, sebastianene@...gle.com, snehalreddy@...gle.com,
sudeep.holla@....com, suzuki.poulose@....com, vdonnefort@...gle.com,
will@...nel.org, yuzenghui@...wei.com
Cc: kvmarm@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com
Subject: [PATCH v3 0/3] KVM: arm64: Separate the hyp FF-A buffers init from
the host
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 ***
v2 -> this version:
- 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 | 24 ------------------------
include/linux/arm_ffa.h | 27 +++++++++++++++++++++++++++
3 files changed, 34 insertions(+), 29 deletions(-)
--
2.49.0.rc1.451.g8f38331e32-goog
Powered by blists - more mailing lists