From: Will Deacon <will@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: catalin.marinas@arm.com, joey.gouly@arm.com, maz@kernel.org,
oliver.upton@linux.dev, snehalreddy@google.com,
sudeep.holla@arm.com, suzuki.poulose@arm.com,
vdonnefort@google.com, yuzenghui@huawei.com,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
Andrei Homescu <ahomescu@google.com>
Subject: Re: [PATCH v2 4/4] KVM: arm64: Release the ownership of the hyp rx buffer to Trustzone
Date: Wed, 5 Mar 2025 00:45:23 +0000 [thread overview]
Message-ID: <20250305004522.GC31667@willie-the-truck> (raw)
In-Reply-To: <20250227181750.3606372-5-sebastianene@google.com>
On Thu, Feb 27, 2025 at 06:17:49PM +0000, Sebastian Ene wrote:
> Introduce the release FF-A call to notify Trustzone that the hypervisor
> has finished copying the data from the buffer shared with Trustzone to
> the non-secure partition.
>
> Reported-by: Andrei Homescu <ahomescu@google.com>
> Signed-off-by: Sebastian Ene <sebastianene@google.com>
> ---
> arch/arm64/kvm/hyp/nvhe/ffa.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
> index 861f24de97cb..7da0203f1ee9 100644
> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
> @@ -725,6 +725,7 @@ static void do_ffa_part_get(struct arm_smccc_res *res,
> DECLARE_REG(u32, uuid3, ctxt, 4);
> DECLARE_REG(u32, flags, ctxt, 5);
> u32 count, partition_sz, copy_sz;
> + struct arm_smccc_res _res;
>
> hyp_spin_lock(&host_buffers.lock);
> if (!host_buffers.rx) {
> @@ -741,7 +742,7 @@ static void do_ffa_part_get(struct arm_smccc_res *res,
>
> count = res->a2;
> if (!count)
> - goto out_unlock;
> + goto release_rx;
>
> if (hyp_ffa_version > FFA_VERSION_1_0) {
> /* Get the number of partitions deployed in the system */
> @@ -757,10 +758,12 @@ static void do_ffa_part_get(struct arm_smccc_res *res,
> copy_sz = partition_sz * count;
> if (copy_sz > KVM_FFA_MBOX_NR_PAGES * PAGE_SIZE) {
> ffa_to_smccc_res(res, FFA_RET_ABORTED);
> - goto out_unlock;
> + goto release_rx;
> }
>
> memcpy(host_buffers.rx, hyp_buffers.rx, copy_sz);
> +release_rx:
> + ffa_rx_release(&_res);
Hmm, the FFA spec is characteristically unclear as to whether or not we
need to release the rx buffer in the case that the flags indicate use of
the rx buffer but the returned partition count is 0.
Sudeep -- do you know what we should be doing in that case?
Will
next prev parent reply other threads:[~2025-03-05 0:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 18:17 [PATCH v2 0/4] KVM: arm64: Separate the hyp FF-A buffers init from the host Sebastian Ene
2025-02-27 18:17 ` [PATCH v2 1/4] KVM: arm64: Use the static initializer for the vesion lock Sebastian Ene
2025-03-05 0:39 ` Will Deacon
2025-02-27 18:17 ` [PATCH v2 2/4] KVM: arm64: Move the ffa_to_linux definition to the ffa header Sebastian Ene
2025-02-27 20:25 ` Sudeep Holla
2025-02-27 23:12 ` Sebastian Ene
2025-02-28 10:09 ` Marc Zyngier
2025-03-03 23:44 ` Will Deacon
2025-03-04 0:38 ` Sebastian Ene
2025-03-04 9:54 ` Sudeep Holla
2025-03-04 9:57 ` Sudeep Holla
2025-02-27 18:17 ` [PATCH v2 3/4] KVM: arm64: Map the hypervisor FF-A buffers on ffa init Sebastian Ene
2025-03-03 23:43 ` Will Deacon
2025-03-04 0:53 ` Sebastian Ene
2025-03-04 1:56 ` Will Deacon
2025-03-04 17:38 ` Sebastian Ene
2025-03-05 0:38 ` Will Deacon
2025-03-05 18:36 ` Sebastian Ene
2025-03-13 12:04 ` Will Deacon
2025-02-27 18:17 ` [PATCH v2 4/4] KVM: arm64: Release the ownership of the hyp rx buffer to Trustzone Sebastian Ene
2025-03-05 0:45 ` Will Deacon [this message]
2025-03-05 9:41 ` Sudeep Holla
2025-03-05 19:34 ` Will Deacon
2025-03-06 9:40 ` Sudeep Holla
2025-03-13 12:15 ` Will Deacon
2025-03-13 14:00 ` Sudeep Holla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250305004522.GC31667@willie-the-truck \
--to=will@kernel.org \
--cc=ahomescu@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=sebastianene@google.com \
--cc=snehalreddy@google.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=yuzenghui@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox