From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Marc Bonnici <marc.bonnici@arm.com>,
Olivier Deprez <Olivier.Deprez@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bertrand Marquis <Bertrand.Marquis@arm.com>,
Jens Wiklander <jens.wiklander@linaro.org>
Subject: Re: [PATCH 3/3] firmware: arm_ffa: Add support for handling notification pending interrupt(NPI)
Date: Thu, 11 Apr 2024 10:54:52 +0100 [thread overview]
Message-ID: <ZhezbKmZenyTJ7js@bogus> (raw)
In-Reply-To: <20240410-ffa_npi_support-v1-3-1a5223391bd1@arm.com>
On Wed, Apr 10, 2024 at 12:39:48PM +0100, Sudeep Holla wrote:
> The FF-A uses the notification pending interrupt to inform the receiver
> that it has a pending notification. This is a virtual interrupt and is
> used by the following type of receivers:
> 1. A guest/VM running under a hypervisor.
> 2. An S-EL1 SP running under a S-EL2 SPMC.
>
> The rules that govern the properties of the NPI are the same as the
> rules for the SRI with couple of exceptions. If the SRI is not supported,
> then an attempt to discover NPI will be made in the driver.
>
> The handling of NPI is also same as the handling of notification for the
> self/primary VM with ID 0 except the absence of global notification.
>
OK I think I rushed to send this. Bertrand had now convinced me with a
use case that needs the support for both SRI and NPI in the driver.
XEN hypervisor can inject both SRI and NPI to the Dom0. The choice of
NPI over SRI is to avoid the context switch latency with the
FFA_NOTIFICATION_INFO_GET as NPI will just need FFA_NOTIFICATION_GET
which may completely avoid switching to secure side as XEN hyp handles
the same.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-11 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 11:39 [PATCH 0/3] firmware: arm_ffa: Add support to run inside a guest/VM under a hypervisor Sudeep Holla
2024-04-10 11:39 ` [PATCH 1/3] firmware: arm_ffa: Skip creation of the notification bitmaps Sudeep Holla
2024-04-10 11:39 ` [PATCH 2/3] firmware: arm_ffa: Rename the references to SRI to include NPI Sudeep Holla
2024-04-10 11:39 ` [PATCH 3/3] firmware: arm_ffa: Add support for handling notification pending interrupt(NPI) Sudeep Holla
2024-04-11 9:54 ` Sudeep Holla [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=ZhezbKmZenyTJ7js@bogus \
--to=sudeep.holla@arm.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Olivier.Deprez@arm.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=marc.bonnici@arm.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).