All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.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>,
	Coboy Chen <coboy.chen@mediatek.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Olivier Deprez <olivier.deprez@arm.com>
Subject: Re: [PATCH v3 07/17] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface
Date: Wed, 4 Oct 2023 11:10:21 +0200	[thread overview]
Message-ID: <20231004091021.GA1091193@rayden> (raw)
In-Reply-To: <20230929-ffa_v1-1_notif-v3-7-c8e4f15190c8@arm.com>

On Fri, Sep 29, 2023 at 04:02:56PM +0100, Sudeep Holla wrote:
> The receiver’s scheduler uses the FFA_NOTIFICATION_INFO_GET interface
> to retrieve the list of endpoints that have pending notifications and
> must be run. A notification could be signaled by a sender in the secure
> world to a VM. The Hypervisor needs to determine which VM and vCPU
> (in case a per-vCPU notification is signaled) has a pending notification
> in this scenario. It must obtain this information through an invocation
> of the FFA_NOTIFICATION_INFO_GET.
> 
> Add the implementation of the NOTIFICATION_INFO_GET interface
> and prepare to use this to handle the schedule receiver interrupt.
> Implementation of handling notifications will be added later.
> 
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>  drivers/firmware/arm_ffa/driver.c | 70 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 70 insertions(+)
> 
> diff --git a/drivers/firmware/arm_ffa/driver.c b/drivers/firmware/arm_ffa/driver.c
> index 02eedb7bc171..dfeeb751bebe 100644
> --- a/drivers/firmware/arm_ffa/driver.c
> +++ b/drivers/firmware/arm_ffa/driver.c
> @@ -602,6 +602,13 @@ static int ffa_notification_bitmap_destroy(void)
>  	(FIELD_PREP(RECEIVER_VCPU_MASK, (vcpu_r)) | \
>  	 FIELD_PREP(RECEIVER_ID_MASK, (r)))
>  
> +#define NOTIFICATION_INFO_GET_MORE_PEND_MASK	BIT(0)
> +#define NOTIFICATION_INFO_GET_ID_COUNT		GENMASK(11, 7)
> +#define ID_LIST_MASK_64				GENMASK(51, 12)
> +#define ID_LIST_MASK_32				GENMASK(31, 12)
> +#define MAX_IDS_64				20
> +#define MAX_IDS_32				10
> +
>  static int ffa_notification_bind_common(u16 dst_id, u64 bitmap,
>  					u32 flags, bool is_bind)
>  {
> @@ -673,6 +680,69 @@ static int ffa_notification_get(u32 flags, struct ffa_notify_bitmaps *notify)
>  	return 0;
>  }
>  
> +static void __do_sched_recv_cb(u16 partition_id, u16 vcpu, bool is_per_vcpu)
> +{
> +	pr_err("Callback for partition 0x%x failed.\n", partition_id);
> +}
> +
> +static void ffa_notification_info_get(bool is_64b)
> +{
> +	int idx, list, max_ids, lists_cnt, ids_processed, ids_count[MAX_IDS_64];
> +	ffa_value_t ret;
> +	u64 id_list;
> +
> +	do {
> +		invoke_ffa_fn((ffa_value_t){
> +			  .a0 = FFA_FN_NATIVE(NOTIFICATION_INFO_GET),
> +			  }, &ret);
> +
> +		if (ret.a0 != FFA_FN_NATIVE(SUCCESS)) {

The specification doesn't require a response using 64-bit SMCCC, it is
valid to respond using 32-bit SMCCC too.

Thanks,
Jens

> +			if (ret.a2 != FFA_RET_NO_DATA)
> +				pr_err("Notification Info fetch failed: 0x%lx (0x%lx)",
> +				       ret.a0, ret.a2);
> +			return;
> +		}
> +
> +		ids_processed = 0;
> +		lists_cnt = FIELD_GET(NOTIFICATION_INFO_GET_ID_COUNT, ret.a2);
> +		if (is_64b) {
> +			max_ids = MAX_IDS_64;
> +			id_list = FIELD_GET(ID_LIST_MASK_64, ret.a2);
> +		} else {
> +			max_ids = MAX_IDS_32;
> +			id_list = FIELD_GET(ID_LIST_MASK_32, ret.a2);
> +		}
> +
> +		for (idx = 0; idx < lists_cnt; idx++, id_list >>= 2)
> +			ids_count[idx] = (id_list & 0x3) + 1;
> +
> +		/* Process IDs */
> +		for (list = 0; list < lists_cnt; list++) {
> +			u16 vcpu_id, part_id, *packed_id_list = (u16 *)&ret.a3;
> +
> +			if (ids_processed >= max_ids - 1)
> +				break;
> +
> +			part_id = packed_id_list[++ids_processed];
> +
> +			if (!ids_count[list]) { /* Global Notification */
> +				__do_sched_recv_cb(part_id, 0, false);
> +				continue;
> +			}
> +
> +			/* Per vCPU Notification */
> +			for (idx = 0; idx < ids_count[list]; idx++) {
> +				if (ids_processed >= max_ids - 1)
> +					break;
> +
> +				vcpu_id = packed_id_list[++ids_processed];
> +
> +				__do_sched_recv_cb(part_id, vcpu_id, true);
> +			}
> +		}
> +	} while (ret.a2 & NOTIFICATION_INFO_GET_MORE_PEND_MASK);
> +}
> +
>  static int ffa_run(struct ffa_device *dev, u16 vcpu)
>  {
>  	ffa_value_t ret;
> 
> -- 
> 2.42.0
> 

_______________________________________________
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: Jens Wiklander <jens.wiklander@linaro.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>,
	Coboy Chen <coboy.chen@mediatek.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Olivier Deprez <olivier.deprez@arm.com>
Subject: Re: [PATCH v3 07/17] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface
Date: Wed, 4 Oct 2023 11:10:21 +0200	[thread overview]
Message-ID: <20231004091021.GA1091193@rayden> (raw)
In-Reply-To: <20230929-ffa_v1-1_notif-v3-7-c8e4f15190c8@arm.com>

On Fri, Sep 29, 2023 at 04:02:56PM +0100, Sudeep Holla wrote:
> The receiver’s scheduler uses the FFA_NOTIFICATION_INFO_GET interface
> to retrieve the list of endpoints that have pending notifications and
> must be run. A notification could be signaled by a sender in the secure
> world to a VM. The Hypervisor needs to determine which VM and vCPU
> (in case a per-vCPU notification is signaled) has a pending notification
> in this scenario. It must obtain this information through an invocation
> of the FFA_NOTIFICATION_INFO_GET.
> 
> Add the implementation of the NOTIFICATION_INFO_GET interface
> and prepare to use this to handle the schedule receiver interrupt.
> Implementation of handling notifications will be added later.
> 
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>  drivers/firmware/arm_ffa/driver.c | 70 +++++++++++++++++++++++++++++++++++++++
>  1 file changed, 70 insertions(+)
> 
> diff --git a/drivers/firmware/arm_ffa/driver.c b/drivers/firmware/arm_ffa/driver.c
> index 02eedb7bc171..dfeeb751bebe 100644
> --- a/drivers/firmware/arm_ffa/driver.c
> +++ b/drivers/firmware/arm_ffa/driver.c
> @@ -602,6 +602,13 @@ static int ffa_notification_bitmap_destroy(void)
>  	(FIELD_PREP(RECEIVER_VCPU_MASK, (vcpu_r)) | \
>  	 FIELD_PREP(RECEIVER_ID_MASK, (r)))
>  
> +#define NOTIFICATION_INFO_GET_MORE_PEND_MASK	BIT(0)
> +#define NOTIFICATION_INFO_GET_ID_COUNT		GENMASK(11, 7)
> +#define ID_LIST_MASK_64				GENMASK(51, 12)
> +#define ID_LIST_MASK_32				GENMASK(31, 12)
> +#define MAX_IDS_64				20
> +#define MAX_IDS_32				10
> +
>  static int ffa_notification_bind_common(u16 dst_id, u64 bitmap,
>  					u32 flags, bool is_bind)
>  {
> @@ -673,6 +680,69 @@ static int ffa_notification_get(u32 flags, struct ffa_notify_bitmaps *notify)
>  	return 0;
>  }
>  
> +static void __do_sched_recv_cb(u16 partition_id, u16 vcpu, bool is_per_vcpu)
> +{
> +	pr_err("Callback for partition 0x%x failed.\n", partition_id);
> +}
> +
> +static void ffa_notification_info_get(bool is_64b)
> +{
> +	int idx, list, max_ids, lists_cnt, ids_processed, ids_count[MAX_IDS_64];
> +	ffa_value_t ret;
> +	u64 id_list;
> +
> +	do {
> +		invoke_ffa_fn((ffa_value_t){
> +			  .a0 = FFA_FN_NATIVE(NOTIFICATION_INFO_GET),
> +			  }, &ret);
> +
> +		if (ret.a0 != FFA_FN_NATIVE(SUCCESS)) {

The specification doesn't require a response using 64-bit SMCCC, it is
valid to respond using 32-bit SMCCC too.

Thanks,
Jens

> +			if (ret.a2 != FFA_RET_NO_DATA)
> +				pr_err("Notification Info fetch failed: 0x%lx (0x%lx)",
> +				       ret.a0, ret.a2);
> +			return;
> +		}
> +
> +		ids_processed = 0;
> +		lists_cnt = FIELD_GET(NOTIFICATION_INFO_GET_ID_COUNT, ret.a2);
> +		if (is_64b) {
> +			max_ids = MAX_IDS_64;
> +			id_list = FIELD_GET(ID_LIST_MASK_64, ret.a2);
> +		} else {
> +			max_ids = MAX_IDS_32;
> +			id_list = FIELD_GET(ID_LIST_MASK_32, ret.a2);
> +		}
> +
> +		for (idx = 0; idx < lists_cnt; idx++, id_list >>= 2)
> +			ids_count[idx] = (id_list & 0x3) + 1;
> +
> +		/* Process IDs */
> +		for (list = 0; list < lists_cnt; list++) {
> +			u16 vcpu_id, part_id, *packed_id_list = (u16 *)&ret.a3;
> +
> +			if (ids_processed >= max_ids - 1)
> +				break;
> +
> +			part_id = packed_id_list[++ids_processed];
> +
> +			if (!ids_count[list]) { /* Global Notification */
> +				__do_sched_recv_cb(part_id, 0, false);
> +				continue;
> +			}
> +
> +			/* Per vCPU Notification */
> +			for (idx = 0; idx < ids_count[list]; idx++) {
> +				if (ids_processed >= max_ids - 1)
> +					break;
> +
> +				vcpu_id = packed_id_list[++ids_processed];
> +
> +				__do_sched_recv_cb(part_id, vcpu_id, true);
> +			}
> +		}
> +	} while (ret.a2 & NOTIFICATION_INFO_GET_MORE_PEND_MASK);
> +}
> +
>  static int ffa_run(struct ffa_device *dev, u16 vcpu)
>  {
>  	ffa_value_t ret;
> 
> -- 
> 2.42.0
> 

  reply	other threads:[~2023-10-04  9:10 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 15:02 [PATCH v3 00/17] firmware: arm_ffa: Add FF-A v1.1 support(notification + new memory descriptor format) Sudeep Holla
2023-09-29 15:02 ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 01/17] firmware: arm_ffa: Update the FF-A command list with v1.1 additions Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 02/17] firmware: arm_ffa: Implement notification bitmap create and destroy interfaces Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 03/17] firmware: arm_ffa: Implement the notification bind and unbind interface Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-10-04  9:11   ` Jens Wiklander
2023-10-04  9:11     ` Jens Wiklander
2023-10-04  9:50     ` Olivier Deprez
2023-10-04  9:50       ` Olivier Deprez
2023-10-04 15:32       ` Sudeep Holla
2023-10-04 15:32         ` Sudeep Holla
2023-10-05  6:57         ` Jens Wiklander
2023-10-05  6:57           ` Jens Wiklander
2023-10-05  8:49           ` Sudeep Holla
2023-10-05  8:49             ` Sudeep Holla
2023-10-05  9:56             ` Jens Wiklander
2023-10-05  9:56               ` Jens Wiklander
2023-10-05 13:30               ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 04/17] firmware: arm_ffa: Implement the FFA_RUN interface Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 05/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 06/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 07/17] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-10-04  9:10   ` Jens Wiklander [this message]
2023-10-04  9:10     ` Jens Wiklander
2023-10-04 15:11     ` Sudeep Holla
2023-10-04 15:11       ` Sudeep Holla
2023-10-05  6:30       ` Jens Wiklander
2023-10-05  6:30         ` Jens Wiklander
2023-09-29 15:02 ` [PATCH v3 08/17] firmware: arm_ffa: Initial support for scheduler receiver interrupt Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 09/17] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 10/17] firmware: arm_ffa: Add interfaces to request notification callbacks Sudeep Holla
2023-09-29 15:02   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 11/17] firmware: arm_ffa: Add interface to send a notification to a given partition Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 12/17] firmware: arm_ffa: Add notification handling mechanism Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 13/17] firmware: arm_ffa: Simplify the computation of transmit and fragment length Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 14/17] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-10-02 16:20   ` Sudeep Holla
2023-10-02 16:20     ` Sudeep Holla
2023-10-04 10:08   ` Marc Zyngier
2023-10-04 10:08     ` Marc Zyngier
2023-10-04 13:22     ` Sudeep Holla
2023-10-04 13:22       ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 15/17] firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 16/17] firmware: arm_ffa: Update memory descriptor to support v1.1 format Sudeep Holla
2023-09-29 15:03   ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 17/17] firmware: arm_ffa: Upgrade the driver version to v1.1 Sudeep Holla
2023-09-29 15:03   ` 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=20231004091021.GA1091193@rayden \
    --to=jens.wiklander@linaro.org \
    --cc=coboy.chen@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=marc.bonnici@arm.com \
    --cc=olivier.deprez@arm.com \
    --cc=sudeep.holla@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 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.