From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ene <sebastianene@google.com>
Cc: catalin.marinas@arm.com, james.morse@arm.com,
jean-philippe@linaro.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, lpieralisi@kernel.org,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v3 0/4] KVM: arm64: pKVM host proxy FF-A fixes
Date: Fri, 14 Jun 2024 14:51:44 +0100 [thread overview]
Message-ID: <86msnnk4y7.wl-maz@kernel.org> (raw)
In-Reply-To: <20240613132035.1070360-1-sebastianene@google.com>
On Thu, 13 Jun 2024 14:20:31 +0100,
Sebastian Ene <sebastianene@google.com> wrote:
>
> Hello,
>
>
> This series contains some small fixes for the host pKVM proxy code. I included
> some of the patches that I already sent on the list as part of this series
> to make it easier to keep track of them.
>
> I verified the functionality with OPTEE as a TEE-OS.
>
> Changelog:
>
> v2 -> v3:
>
> * small fixes on the commit messages
> * applied the Review-by tags from Sudeep. Thank you Sudeep !
>
> v1 -> v2:
>
> * applied the feedback received from Will on the FFA_VERSION patch:
> The spec requires that no other calls to be issued prior to the FFA
> version negotiation and the current change reflects this. After the
> version negotiation phase is complete with Trustzone we will just
> return the hypervisor version.
>
> * corrected some mistakes on the FFA_PARTITION_INFO_GET patch:
> - don't trim the number of bytes copied from the hypervisor buffer
> - introduce FFA_1_0_PARTITON_INFO_SZ definition
> - simplify the logic when the input flag is specified
>
> * collected the Ack from Will and embbeded it in the commit - Thanks Will !
>
>
> v2:
> https://lore.kernel.org/all/20240515172258.1680881-1-sebastianene@google.com/
>
> v1:
>
> * previously posted FFA_PARTITION_INFO_GET patch here:
> https://lore.kernel.org/kvmarm/20240411133249.2134696-1-sebastianene@google.com/
> -> minor changes from the previous version, look for the current
> ffa_version in the host_buffer structure
>
> * previously posted "Fix the identification range for the FF-A smcs" here:
> https://lore.kernel.org/kvmarm/20240322124303.309423-1-sebastianene@google.com/
>
> Thank you,
> Sebastian
>
> Sebastian Ene (4):
> KVM: arm64: Trap FFA_VERSION host call in pKVM
> KVM: arm64: Add support for FFA_PARTITION_INFO_GET
> KVM: arm64: Update the identification range for the FF-A smcs
> KVM: arm64: Use FF-A 1.1 with pKVM
>
> arch/arm64/kvm/hyp/include/nvhe/ffa.h | 2 +-
> arch/arm64/kvm/hyp/nvhe/ffa.c | 180 +++++++++++++++++++++-----
> include/linux/arm_ffa.h | 3 +
> 3 files changed, 152 insertions(+), 33 deletions(-)
Although these are labelled as fixes, I don't think they warrant being
taken into 6.10. So assuming Oliver will take them into 6.11:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-06-14 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:20 [PATCH v3 0/4] KVM: arm64: pKVM host proxy FF-A fixes Sebastian Ene
2024-06-13 13:20 ` [PATCH v3 1/4] KVM: arm64: Trap FFA_VERSION host call in pKVM Sebastian Ene
2024-06-13 13:20 ` [PATCH v3 2/4] KVM: arm64: Add support for FFA_PARTITION_INFO_GET Sebastian Ene
2024-06-13 13:20 ` [PATCH v3 3/4] KVM: arm64: Update the identification range for the FF-A smcs Sebastian Ene
2024-06-13 13:20 ` [PATCH v3 4/4] KVM: arm64: Use FF-A 1.1 with pKVM Sebastian Ene
2024-06-14 13:51 ` Marc Zyngier [this message]
2024-06-17 17:23 ` [PATCH v3 0/4] KVM: arm64: pKVM host proxy FF-A fixes Oliver Upton
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=86msnnk4y7.wl-maz@kernel.org \
--to=maz@kernel.org \
--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=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=qwandor@google.com \
--cc=sebastianene@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).