From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"patches@linaro.org" <patches@linaro.org>,
Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Michal Orzel <michal.orzel@amd.com>
Subject: Re: [XEN PATCH v3 0/5] FF-A notifications
Date: Fri, 26 Apr 2024 09:23:22 +0000 [thread overview]
Message-ID: <9094E02F-B4EF-4E22-8DEA-179AAA4CACE0@arm.com> (raw)
In-Reply-To: <20240426084723.4149648-1-jens.wiklander@linaro.org>
Hi Jens
> On 26 Apr 2024, at 10:47, Jens Wiklander <jens.wiklander@linaro.org> wrote:
>
> Hi,
>
> This patch set adds support for FF-A notifications. We only support
> global notifications, per vCPU notifications remain unsupported.
>
> The first three patches are further cleanup and can be merged before the
> rest if desired.
>
> A physical SGI is used to make Xen aware of pending FF-A notifications. The
> physical SGI is selected by the SPMC in the secure world. Since it must not
> already be used by Xen the SPMC is in practice forced to donate one of the
> secure SGIs, but that's normally not a problem. The SGI handling in Xen is
> updated to support registration of handlers for SGIs that aren't statically
> assigned, that is, SGI IDs above GIC_SGI_MAX.
From my point of view:
- patches 1 to 3 are ready to be commited.
- patch 4 will need a R-b from an other maintainer.
- patch 5 has still some stuff to be checked or fixed but could be
handled as a single patch if the rest or the serie is merged.
Regards
Bertrand
>
> Thanks,
> Jens
>
> v2->v3:
> - "xen/arm: ffa: support notification" and
> "xen/arm: allow dynamically assigned SGI handlers" updated as requestsed,
> details in each patch.
>
> v1->v2:
> - "xen/arm: ffa: support notification" and
> "xen/arm: allow dynamically assigned SGI handlers" updated as requestsed,
> details in each patch.
> - Added Bertrands R-B for "xen/arm: ffa: refactor ffa_handle_call()",
> "xen/arm: ffa: use ACCESS_ONCE()", and
> "xen/arm: ffa: simplify ffa_handle_mem_share()"
>
> Jens Wiklander (5):
> xen/arm: ffa: refactor ffa_handle_call()
> xen/arm: ffa: use ACCESS_ONCE()
> xen/arm: ffa: simplify ffa_handle_mem_share()
> xen/arm: allow dynamically assigned SGI handlers
> xen/arm: ffa: support notification
>
> xen/arch/arm/gic.c | 12 +-
> xen/arch/arm/include/asm/gic.h | 2 +-
> xen/arch/arm/irq.c | 18 +-
> xen/arch/arm/tee/Makefile | 1 +
> xen/arch/arm/tee/ffa.c | 83 +++++--
> xen/arch/arm/tee/ffa_notif.c | 378 ++++++++++++++++++++++++++++++++
> xen/arch/arm/tee/ffa_partinfo.c | 9 +-
> xen/arch/arm/tee/ffa_private.h | 56 ++++-
> xen/arch/arm/tee/ffa_shm.c | 33 ++-
> xen/include/public/arch-arm.h | 14 ++
> 10 files changed, 551 insertions(+), 55 deletions(-)
> create mode 100644 xen/arch/arm/tee/ffa_notif.c
>
> --
> 2.34.1
>
prev parent reply other threads:[~2024-04-26 9:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 8:47 [XEN PATCH v3 0/5] FF-A notifications Jens Wiklander
2024-04-26 8:47 ` [XEN PATCH v3 1/5] xen/arm: ffa: refactor ffa_handle_call() Jens Wiklander
2024-04-26 8:47 ` [XEN PATCH v3 2/5] xen/arm: ffa: use ACCESS_ONCE() Jens Wiklander
2024-04-26 8:47 ` [XEN PATCH v3 3/5] xen/arm: ffa: simplify ffa_handle_mem_share() Jens Wiklander
2024-04-26 8:47 ` [XEN PATCH v3 4/5] xen/arm: allow dynamically assigned SGI handlers Jens Wiklander
2024-04-26 8:47 ` [XEN PATCH v3 5/5] xen/arm: ffa: support notification Jens Wiklander
2024-04-26 9:20 ` Bertrand Marquis
2024-04-26 12:11 ` Jens Wiklander
2024-04-26 12:19 ` Bertrand Marquis
2024-04-26 12:32 ` Jens Wiklander
2024-04-26 12:41 ` Bertrand Marquis
2024-04-26 13:02 ` Jens Wiklander
2024-04-26 15:12 ` Bertrand Marquis
2024-04-26 18:31 ` Julien Grall
2024-04-26 17:58 ` Julien Grall
2024-04-29 9:55 ` Jens Wiklander
2024-04-26 19:07 ` Julien Grall
2024-04-29 7:20 ` Bertrand Marquis
2024-04-29 9:49 ` Jens Wiklander
2024-04-29 20:55 ` Julien Grall
2024-04-29 8:43 ` Jens Wiklander
2024-04-26 9:23 ` Bertrand Marquis [this message]
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=9094E02F-B4EF-4E22-8DEA-179AAA4CACE0@arm.com \
--to=bertrand.marquis@arm.com \
--cc=jens.wiklander@linaro.org \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=patches@linaro.org \
--cc=sstabellini@kernel.org \
--cc=volodymyr_babchuk@epam.com \
--cc=xen-devel@lists.xenproject.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.