From: Per Larsen <perl@immunant.com>
To: Will Deacon <will@kernel.org>, perlarsen@google.com
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Yeoreum Yun <yeoreum.yun@arm.com>,
Ben Horgan <ben.horgan@arm.com>, Oliver Upton <oupton@kernel.org>,
Armelle Laine <armellel@google.com>,
Sebastien Ene <sebastianene@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] KVM: arm64: Support FFA_MSG_SEND_DIRECT_REQ in host handler
Date: Thu, 30 Apr 2026 19:18:46 -0700 [thread overview]
Message-ID: <635b64dc-0083-4421-9145-59636c4ac7cc@immunant.com> (raw)
In-Reply-To: <aXNvzxoBXr-oRB8r@willie-the-truck>
On 1/23/26 4:55 AM, Will Deacon wrote:
> Per,
>
> On Wed, Jan 21, 2026 at 08:27:12AM +0000, Per Larsen via B4 Relay wrote:
>> From: Sebastian Ene <sebastianene@google.com>
>>
>> Allow direct messages to be forwarded from the host. The host should
>> not be sending framework messages so they are filtered out.
>>
>> Signed-off-by: Sebastian Ene <sebastianene@google.com>
>> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com>
>> Signed-off-by: Per Larsen <perlarsen@google.com>
>> ---
>> arch/arm64/kvm/hyp/nvhe/ffa.c | 26 ++++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
>> index f731cc4c3f280a32acccca0de92b9ac6c8e05602..9967916278a7ca051500946ef2fcfe7bb40e0e8d 100644
>> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
>> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
>> @@ -862,6 +862,28 @@ static void do_ffa_part_get(struct arm_smccc_1_2_regs *res,
>> hyp_spin_unlock(&host_buffers.lock);
>> }
>>
>> +static void do_ffa_direct_msg(struct arm_smccc_1_2_regs *res,
>> + struct kvm_cpu_context *ctxt,
>> + u64 vm_handle)
>> +{
>> + DECLARE_REG(u32, flags, ctxt, 2);
>> +
>> + struct arm_smccc_1_2_regs *args = (void *)&ctxt->regs.regs[0];
>> +
>> + if (vm_handle != HOST_FFA_ID) {
>> + ffa_to_smccc_error(res, FFA_RET_INVALID_PARAMETERS);
>> + return;
>> + }
>
> Sorry, but this isn't what I had in mind. 'vm_handle' is just a local
> variable and the only caller passes HOST_FFA_ID, so this isn't really
> achieving anything.
>
> What you had in v4 dropped the 'vm_handle' argument entirely, which I
> think is the right thing to do. However, the FF-A spec encodes the sender
> ID in bits 31:16 of register W1 and so _that_ is what I think we should
> be checking because _that_ is what the receiver will see.
I should have read your feedback more closely and checked against the
spec. I will add a new mask for bits 31:16 to check sender ID against
HOST_FFA_ID. Sorry to waste a review cycle and your attention on this.
> Honestly, we could avoid quite a lot of these review cycles if you
> actually replied to my emails on the list instead of just responding
> with a new patch series each time. It's supposed to be a technical
> discussion...
Acknowledged; will do! Apologies for the very late reply.
next prev parent reply other threads:[~2026-05-01 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 8:27 [PATCH v5 0/2] KVM: arm64: Support FF-A direct messaging interfaces Per Larsen via B4 Relay
2026-01-21 8:27 ` [PATCH v5 1/2] KVM: arm64: Support FFA_MSG_SEND_DIRECT_REQ in host handler Per Larsen via B4 Relay
2026-01-23 12:55 ` Will Deacon
2026-05-01 2:18 ` Per Larsen [this message]
2026-01-21 8:27 ` [PATCH v5 2/2] KVM: arm64: Support FFA_MSG_SEND_DIRECT_REQ2 " Per Larsen via B4 Relay
2026-04-30 21:40 ` [PATCH v5 0/2] KVM: arm64: Support FF-A direct messaging interfaces Yeoreum Yun
2026-05-01 2:30 ` Per Larsen
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=635b64dc-0083-4421-9145-59636c4ac7cc@immunant.com \
--to=perl@immunant.com \
--cc=armellel@google.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=perlarsen@google.com \
--cc=sebastianene@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.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