From: Marc Zyngier <maz@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Marc Bonnici <marc.bonnici@arm.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Coboy Chen <coboy.chen@mediatek.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Olivier Deprez <olivier.deprez@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Will Deacon <will@kernel.org>,
Quentin Perret <qperret@google.com>
Subject: Re: [PATCH v4 14/17] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array
Date: Fri, 06 Oct 2023 19:25:49 +0100 [thread overview]
Message-ID: <878r8fmwuq.wl-maz@kernel.org> (raw)
In-Reply-To: <20231005-ffa_v1-1_notif-v4-14-cddd3237809c@arm.com>
On Thu, 05 Oct 2023 15:45:07 +0100,
Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> FF-A v1.1 removes the fixed location of endpoint memory access descriptor
> array within the memory transaction descriptor structure. In preparation
> to remove the ep_mem_access member from the ffa_mem_region structure,
> provide the accessor to fetch the offset and use the same in FF-A proxy
> implementation.
>
> The accessor take the FF-A version as the argument from which the memory
> access descriptor format can be determined. v1.0 uses the old format while
> v1.1 onwards use the new format specified in the v1.1 specification.
>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: Will Deacon <will@kernel.org>
> Cc: Quentin Perret <qperret@google.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> arch/arm64/kvm/hyp/nvhe/ffa.c | 10 ++++++++--
> include/linux/arm_ffa.h | 6 ++++++
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
> index 6e4dba9eadef..320f2eaa14a9 100644
> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
> @@ -423,6 +423,7 @@ static __always_inline void do_ffa_mem_xfer(const u64 func_id,
> DECLARE_REG(u32, fraglen, ctxt, 2);
> DECLARE_REG(u64, addr_mbz, ctxt, 3);
> DECLARE_REG(u32, npages_mbz, ctxt, 4);
> + struct ffa_mem_region_attributes *ep_mem_access;
> struct ffa_composite_mem_region *reg;
> struct ffa_mem_region *buf;
> u32 offset, nr_ranges;
> @@ -452,7 +453,9 @@ static __always_inline void do_ffa_mem_xfer(const u64 func_id,
> buf = hyp_buffers.tx;
> memcpy(buf, host_buffers.tx, fraglen);
>
> - offset = buf->ep_mem_access[0].composite_off;
> + ep_mem_access = (void *)buf +
> + ffa_mem_desc_offset(buf, 0, FFA_VERSION_1_0);
> + offset = ep_mem_access->composite_off;
> if (!offset || buf->ep_count != 1 || buf->sender_id != HOST_FFA_ID) {
> ret = FFA_RET_INVALID_PARAMETERS;
> goto out_unlock;
> @@ -504,6 +507,7 @@ static void do_ffa_mem_reclaim(struct arm_smccc_res *res,
> DECLARE_REG(u32, handle_lo, ctxt, 1);
> DECLARE_REG(u32, handle_hi, ctxt, 2);
> DECLARE_REG(u32, flags, ctxt, 3);
> + struct ffa_mem_region_attributes *ep_mem_access;
> struct ffa_composite_mem_region *reg;
> u32 offset, len, fraglen, fragoff;
> struct ffa_mem_region *buf;
> @@ -528,7 +532,9 @@ static void do_ffa_mem_reclaim(struct arm_smccc_res *res,
> len = res->a1;
> fraglen = res->a2;
>
> - offset = buf->ep_mem_access[0].composite_off;
> + ep_mem_access = (void *)buf +
> + ffa_mem_desc_offset(buf, 0, FFA_VERSION_1_0);
> + offset = ep_mem_access->composite_off;
> /*
> * We can trust the SPMD to get this right, but let's at least
> * check that we end up with something that doesn't look _completely_
> diff --git a/include/linux/arm_ffa.h b/include/linux/arm_ffa.h
> index 748d0a83a4bc..2444d596b703 100644
> --- a/include/linux/arm_ffa.h
> +++ b/include/linux/arm_ffa.h
> @@ -357,6 +357,12 @@ struct ffa_mem_region {
> #define CONSTITUENTS_OFFSET(x) \
> (offsetof(struct ffa_composite_mem_region, constituents[x]))
>
> +static inline u32
> +ffa_mem_desc_offset(struct ffa_mem_region *buf, int count, u32 ffa_version)
> +{
> + return COMPOSITE_OFFSET(0);
> +}
> +
> struct ffa_mem_ops_args {
> bool use_txbuf;
> u32 nattrs;
>
I haven't looked at the rest of the series, but for the purpose of
this particular patch, it looks OK to me.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Marc Bonnici <marc.bonnici@arm.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Coboy Chen <coboy.chen@mediatek.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Olivier Deprez <olivier.deprez@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Will Deacon <will@kernel.org>,
Quentin Perret <qperret@google.com>
Subject: Re: [PATCH v4 14/17] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array
Date: Fri, 06 Oct 2023 19:25:49 +0100 [thread overview]
Message-ID: <878r8fmwuq.wl-maz@kernel.org> (raw)
In-Reply-To: <20231005-ffa_v1-1_notif-v4-14-cddd3237809c@arm.com>
On Thu, 05 Oct 2023 15:45:07 +0100,
Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> FF-A v1.1 removes the fixed location of endpoint memory access descriptor
> array within the memory transaction descriptor structure. In preparation
> to remove the ep_mem_access member from the ffa_mem_region structure,
> provide the accessor to fetch the offset and use the same in FF-A proxy
> implementation.
>
> The accessor take the FF-A version as the argument from which the memory
> access descriptor format can be determined. v1.0 uses the old format while
> v1.1 onwards use the new format specified in the v1.1 specification.
>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: Will Deacon <will@kernel.org>
> Cc: Quentin Perret <qperret@google.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> arch/arm64/kvm/hyp/nvhe/ffa.c | 10 ++++++++--
> include/linux/arm_ffa.h | 6 ++++++
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
> index 6e4dba9eadef..320f2eaa14a9 100644
> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
> @@ -423,6 +423,7 @@ static __always_inline void do_ffa_mem_xfer(const u64 func_id,
> DECLARE_REG(u32, fraglen, ctxt, 2);
> DECLARE_REG(u64, addr_mbz, ctxt, 3);
> DECLARE_REG(u32, npages_mbz, ctxt, 4);
> + struct ffa_mem_region_attributes *ep_mem_access;
> struct ffa_composite_mem_region *reg;
> struct ffa_mem_region *buf;
> u32 offset, nr_ranges;
> @@ -452,7 +453,9 @@ static __always_inline void do_ffa_mem_xfer(const u64 func_id,
> buf = hyp_buffers.tx;
> memcpy(buf, host_buffers.tx, fraglen);
>
> - offset = buf->ep_mem_access[0].composite_off;
> + ep_mem_access = (void *)buf +
> + ffa_mem_desc_offset(buf, 0, FFA_VERSION_1_0);
> + offset = ep_mem_access->composite_off;
> if (!offset || buf->ep_count != 1 || buf->sender_id != HOST_FFA_ID) {
> ret = FFA_RET_INVALID_PARAMETERS;
> goto out_unlock;
> @@ -504,6 +507,7 @@ static void do_ffa_mem_reclaim(struct arm_smccc_res *res,
> DECLARE_REG(u32, handle_lo, ctxt, 1);
> DECLARE_REG(u32, handle_hi, ctxt, 2);
> DECLARE_REG(u32, flags, ctxt, 3);
> + struct ffa_mem_region_attributes *ep_mem_access;
> struct ffa_composite_mem_region *reg;
> u32 offset, len, fraglen, fragoff;
> struct ffa_mem_region *buf;
> @@ -528,7 +532,9 @@ static void do_ffa_mem_reclaim(struct arm_smccc_res *res,
> len = res->a1;
> fraglen = res->a2;
>
> - offset = buf->ep_mem_access[0].composite_off;
> + ep_mem_access = (void *)buf +
> + ffa_mem_desc_offset(buf, 0, FFA_VERSION_1_0);
> + offset = ep_mem_access->composite_off;
> /*
> * We can trust the SPMD to get this right, but let's at least
> * check that we end up with something that doesn't look _completely_
> diff --git a/include/linux/arm_ffa.h b/include/linux/arm_ffa.h
> index 748d0a83a4bc..2444d596b703 100644
> --- a/include/linux/arm_ffa.h
> +++ b/include/linux/arm_ffa.h
> @@ -357,6 +357,12 @@ struct ffa_mem_region {
> #define CONSTITUENTS_OFFSET(x) \
> (offsetof(struct ffa_composite_mem_region, constituents[x]))
>
> +static inline u32
> +ffa_mem_desc_offset(struct ffa_mem_region *buf, int count, u32 ffa_version)
> +{
> + return COMPOSITE_OFFSET(0);
> +}
> +
> struct ffa_mem_ops_args {
> bool use_txbuf;
> u32 nattrs;
>
I haven't looked at the rest of the series, but for the purpose of
this particular patch, it looks OK to me.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-10-06 18:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 14:44 [PATCH v4 00/17] firmware: arm_ffa: Add FF-A v1.1 support(notification + new memory descriptor format) Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 01/17] firmware: arm_ffa: Update the FF-A command list with v1.1 additions Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 02/17] firmware: arm_ffa: Implement notification bitmap create and destroy interfaces Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 03/17] firmware: arm_ffa: Implement the notification bind and unbind interface Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 04/17] firmware: arm_ffa: Implement the FFA_RUN interface Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 05/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:44 ` [PATCH v4 06/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface Sudeep Holla
2023-10-05 14:44 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 07/17] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 08/17] firmware: arm_ffa: Initial support for scheduler receiver interrupt Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 09/17] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 10/17] firmware: arm_ffa: Add interfaces to request notification callbacks Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 11/17] firmware: arm_ffa: Add interface to send a notification to a given partition Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 12/17] firmware: arm_ffa: Add notification handling mechanism Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 13/17] firmware: arm_ffa: Simplify the computation of transmit and fragment length Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 14/17] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-06 15:25 ` Sudeep Holla
2023-10-06 15:25 ` Sudeep Holla
2023-10-06 18:25 ` Marc Zyngier [this message]
2023-10-06 18:25 ` Marc Zyngier
2023-10-05 14:45 ` [PATCH v4 15/17] firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 16/17] firmware: arm_ffa: Update memory descriptor to support v1.1 format Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-05 14:45 ` [PATCH v4 17/17] firmware: arm_ffa: Upgrade the driver version to v1.1 Sudeep Holla
2023-10-05 14:45 ` Sudeep Holla
2023-10-09 11:49 ` [PATCH v4 00/17] firmware: arm_ffa: Add FF-A v1.1 support(notification + new memory descriptor format) Sudeep Holla
2023-10-09 11:49 ` 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=878r8fmwuq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=coboy.chen@mediatek.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=marc.bonnici@arm.com \
--cc=oliver.upton@linux.dev \
--cc=olivier.deprez@arm.com \
--cc=qperret@google.com \
--cc=sudeep.holla@arm.com \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.