From: Sebastian Ene <sebastianene@google.com>
To: Per Larsen <perl@immunant.com>
Cc: linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
james.morse@arm.com, jean-philippe@linaro.org,
kernel-team@android.com, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, lpieralisi@kernel.org,
maz@kernel.org, oliver.upton@linux.dev, qperret@google.com,
qwandor@google.com, sudeep.holla@arm.com, suzuki.poulose@arm.com,
tabba@google.com, will@kernel.org, yuzenghui@huawei.com,
armellel@google.com, arve@android.com, ahomescu@google.com
Subject: Re: [PATCH 0/3] KVM: arm64: Support FF-A 1.2 and SEND_DIRECT2 ABI
Date: Fri, 2 May 2025 10:35:45 +0000 [thread overview]
Message-ID: <aBSgAScZUp9qIspT@google.com> (raw)
In-Reply-To: <20250502092108.3224341-1-perl@immunant.com>
On Fri, May 02, 2025 at 02:21:05AM -0700, Per Larsen wrote:
> Hi,
>
> The FF-A 1.2 specification introduces a new SEND_DIRECT2 ABI which
> allows registers x4-x17 to be used for the message payload. This patch
> set prevents the host from using a lower FF-A version than what has
> already been negotiated with the hypervisor. This is necessary because
> the hypervisor does not have the necessary compatibility paths to
> translate from the hypervisor FF-A version to a previous version.
>
> Support for FF-A 1.2 in the hypervisor is added as a precursor to the
> addition of the FFA_MSG_SEND_DIRECT_REQ2 messaging interface. The bulk
> of this change has to do with the upgrade to SMCCC 1.2 required by
> FF-A 1.2. Additionally, unimplemented FF-A 1.2 interfaces are added to
> the list of unsupported functions.
>
> Tested by booting Android under QEMU and loading Trusty as the guest
> VM and observing the SEND_DIRECT2 ABI being used successfully during
> guest boot.
>
> (This is my second attempt at sending out these patches; sorry about
> my broken first try and the resulting duplicate messages.)
Please tag this series with v2 if this is the second one and include a
changelog.
>
> Thanks,
> Per Larsen
>
> Per Larsen (3):
> KVM: arm64: Restrict FF-A host version renegotiation
> KVM: arm64: Bump the supported version of FF-A to 1.2
> KVM: arm64: Support FFA_MSG_SEND_DIRECT_REQ2 in host handler
>
> arch/arm64/kvm/hyp/nvhe/Makefile | 1 +
> arch/arm64/kvm/hyp/nvhe/ffa.c | 235 ++++++++++++++++++++++++++++---
> include/linux/arm_ffa.h | 2 +
> 3 files changed, 221 insertions(+), 17 deletions(-)
>
> --
> 2.49.0
>
Thanks,
Seb
next prev parent reply other threads:[~2025-05-02 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 9:21 [PATCH 0/3] KVM: arm64: Support FF-A 1.2 and SEND_DIRECT2 ABI Per Larsen
2025-05-02 9:21 ` [PATCH 1/3] KVM: arm64: Restrict FF-A host version renegotiation Per Larsen
2025-05-06 10:10 ` Sebastian Ene
2025-05-02 9:21 ` [PATCH 2/3] KVM: arm64: Bump the supported version of FF-A to 1.2 Per Larsen
2025-05-06 12:01 ` Sebastian Ene
2025-05-02 9:21 ` [PATCH 3/3] KVM: arm64: Support FFA_MSG_SEND_DIRECT_REQ2 in host handler Per Larsen
2025-05-06 12:16 ` Sebastian Ene
2025-05-02 10:35 ` Sebastian Ene [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-02 3:49 [PATCH 0/3] KVM: arm64: Support FF-A 1.2 and SEND_DIRECT2 ABI 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=aBSgAScZUp9qIspT@google.com \
--to=sebastianene@google.com \
--cc=ahomescu@google.com \
--cc=armellel@google.com \
--cc=arve@android.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=perl@immunant.com \
--cc=qperret@google.com \
--cc=qwandor@google.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).