From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f180.google.com (mail-pg1-f180.google.com [209.85.215.180]) by mx.groups.io with SMTP id smtpd.web10.1581.1689182019450250170 for ; Wed, 12 Jul 2023 10:13:39 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20221208 header.b=X5p1Ikgw; spf=pass (domain: gmail.com, ip: 209.85.215.180, mailfrom: kuqin12@gmail.com) Received: by mail-pg1-f180.google.com with SMTP id 41be03b00d2f7-55b66ca1c80so3834547a12.0 for ; Wed, 12 Jul 2023 10:13:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689182019; x=1691774019; h=in-reply-to:content-language:from:references:cc:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=PpqlPD1lBhQXXy7DoNVEEbW5oWV8LiUO8M9IlcSkoik=; b=X5p1Ikgwu1JQ1/r8dhZ8KhU8CfRTALpkgiO11LSXHpsRuV2TFOq5eeU95Rh7xnX2vZ cSo1++Y3ZQckgoOq6tcQti1juqzO3kaQl1u6pAJHUDOX0qNMVUgIreKD5OkPUCBsRmd2 suaLhQVZGRg0//AzVsz9cTh1xFxCVao8Hgr3YjyUSuJekuwYP9HsNdgAuulCo76+EI1Y Yi5olFy0ctt9cwGHEVayP3PHydeV7FPyXnJH3TTPfFJALgCsqLgdVLqCwQINXanAZGr2 ux24pjpmW3AVZwz+OfjiFNJ6wq3GnM35KKLTROCzWsuSrd2i/iIWVl0S1b38ob8UicCO 3unA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689182019; x=1691774019; h=in-reply-to:content-language:from:references:cc:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=PpqlPD1lBhQXXy7DoNVEEbW5oWV8LiUO8M9IlcSkoik=; b=DPAvl2fTeHnl8UXWt3bRyI3XHOGoggZZb0cmfoIs9BTiOY3DVi0OvEGlvbC9I5y2mQ 8ePsgqecR6gkcIKdSAL+eLiTLgfXWuKlG9HVMJLYGdu1LEXU1c4bXM9OF0VHwLje1oLn y1wjbacxZfiECSwYiw1J+XhusMuIcgve9kRt0mjiKuAZphAItmsESvgN/NDjCxoe5H6R 3RzrITFitlaPh+KSF0SX+cmKNZxZsgcWAfPVnANJogwGskG5YSlDnPnplqw4wpOlItJ2 sCIoZhEf/LyS6jDGY1SzZGGpbfKMbQBdw60/9U/Z3026I4+rPJeYQCMLfz4oU+a856JX 5EGg== X-Gm-Message-State: ABy/qLYFdU8DIXUDM4JL53PCEOH0sQCWEyZyqnDGiM3b00F5BqpoDjH9 6BeLP7lyJbcrLAh0+gog1Fo= X-Google-Smtp-Source: APBJJlEWVdJFkh+Rm9ykoyI+0lkqgS3QXy+NwaPe9QmLzI4kn+lhtBH+gseVx99BchlUT1mEhg5ZMw== X-Received: by 2002:a17:902:8ec8:b0:1b9:e0cc:1810 with SMTP id x8-20020a1709028ec800b001b9e0cc1810mr7783924plo.48.1689182018561; Wed, 12 Jul 2023 10:13:38 -0700 (PDT) Return-Path: Received: from ?IPV6:2001:4898:d8:33:3d92:ee19:1ba0:6377? ([2001:4898:80e8:1:bdb3:ee19:1ba0:6377]) by smtp.gmail.com with ESMTPSA id jw16-20020a170903279000b001b8b45b177esm4190667plb.274.2023.07.12.10.13.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 12 Jul 2023 10:13:38 -0700 (PDT) Message-ID: Date: Wed, 12 Jul 2023 10:13:37 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 19/20] ArmPkg/MmCommunicationDxe: Use the FF-A transport for MM requests To: Achin Gupta , "devel@edk2.groups.io" , Nishant Sharma Cc: Ard Biesheuvel , Sami Mujawar , Thomas Abraham , Sayanta Pattanayak , Aditya Angadi , nd References: <20230711143658.781597-1-nishant.sharma@arm.com> <20230711143658.781597-20-nishant.sharma@arm.com> From: "Kun Qin" In-Reply-To: Content-Type: multipart/alternative; boundary="------------phtGgUN5Qovo0kIPQ8G1KL00" Content-Language: en-US --------------phtGgUN5Qovo0kIPQ8G1KL00 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Achin, The main MM communicate usage in PEI we have today is the variable service, because non secure UEFI cannot access flash directly. We had a few use cases where we need to check the variable from the previous boot in PEI, update some configuration data and consume it for the rest of the boot. I think it will break as is if we switch over to FFA aware framework? Please let me know how you think about the potential support in PEI. Regards, Kun On 7/12/2023 7:21 AM, Achin Gupta wrote: > Hi Kun, > > IIUC, not much happens during the PEI phase on Arm platforms. Hence > the patches focus on DXE in the Normal world. It would be difficult to > provide an effort estimate as we do not see a use case and > consequently this is not on the to-do list. Would you be able to > provide more detail about the scenarios you have in mind? > > cheers, > Achin > ------------------------------------------------------------------------ > *From:* Kun Qin > *Sent:* 11 July 2023 20:22 > *To:* devel@edk2.groups.io ; Nishant Sharma > > *Cc:* Ard Biesheuvel ; Sami Mujawar > ; Thomas Abraham ; > Sayanta Pattanayak ; Achin Gupta > ; Aditya Angadi > *Subject:* Re: [edk2-devel] [edk2-platforms][PATCH V1 19/20] > ArmPkg/MmCommunicationDxe: Use the FF-A transport for MM requests > Hi Nishant, > > Thank you for sending out the patch. Can you please evaluate how much > effort it would be > to support the same for MmCommunicatePei? I think it would provide > better coverage for > the FFA support if we can have that change. > > Thanks, > Kun > > On 7/11/2023 7:36 AM, Nishant Sharma wrote: > > From: Achin Gupta > > > > This patch packages requests for accessing a Standalone MM driver > > through the MM communication protocol as FF-A direct messages. > > Corresponding changes in Standalone MM Core ensure that responses are > > packaged in the same way. > > > > Signed-off-by: Achin Gupta > > Co-developed-by: Aditya Angadi > > Signed-off-by: Nishant Sharma > > --- > >   ArmPkg/Include/IndustryStandard/ArmFfaSvc.h |   2 + > >   ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c | 141 > +++++++++++++------- > >   2 files changed, 97 insertions(+), 46 deletions(-) > > > > diff --git a/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h > b/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h > > index 530af8bd3c2e..493997346143 100644 > > --- a/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h > > +++ b/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h > > @@ -23,6 +23,7 @@ > >   #define ARM_SVC_ID_FFA_RXTX_UNMAP_AARCH32            0x84000067 > >   #define ARM_SVC_ID_FFA_PARTITION_INFO_GET_AARCH32    0x84000068 > >   #define ARM_SVC_ID_FFA_ID_GET_AARCH32                0x84000069 > > +#define ARM_SVC_ID_FFA_RUN_AARCH32 0x8400006D > >   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH32   0x8400006F > >   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_RESP_AARCH32  0x84000070 > >   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH64   0xC400006F > > @@ -31,6 +32,7 @@ > >   #define ARM_SVC_ID_FFA_SUCCESS_AARCH64               0xC4000061 > >   #define ARM_SVC_ID_FFA_MEM_PERM_SET_AARCH32          0x84000089 > >   #define ARM_SVC_ID_FFA_MEM_PERM_GET_AARCH32          0x84000088 > > +#define ARM_SVC_ID_FFA_INTERRUPT_AARCH32 0x84000062 > >   #define ARM_SVC_ID_FFA_ERROR_AARCH32                 0x84000060 > >   #define ARM_SVC_ID_FFA_ERROR_AARCH64                 0xC4000060 > >   #define ARM_SVC_ID_FFA_MSG_WAIT_AARCH32              0x8400006B > > diff --git a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c > b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c > > index 94a5d96c051d..a70318581bd2 100644 > > --- a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c > > +++ b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c > > @@ -100,6 +100,7 @@ MmCommunication2Communicate ( > >     ARM_SMC_ARGS               CommunicateSmcArgs; > >     EFI_STATUS                 Status; > >     UINTN                      BufferSize; > > +  UINTN                      Ret; > > > >     Status     = EFI_ACCESS_DENIED; > >     BufferSize = 0; > > @@ -160,60 +161,108 @@ MmCommunication2Communicate ( > >       return Status; > >     } > > > > -  // SMC Function ID > > -  CommunicateSmcArgs.Arg0 = ARM_SMC_ID_MM_COMMUNICATE_AARCH64; > > - > > -  // Cookie > > -  CommunicateSmcArgs.Arg1 = 0; > > - > >     // Copy Communication Payload > >     CopyMem ((VOID *)mNsCommBuffMemRegion.VirtualBase, > CommBufferVirtual, BufferSize); > > > > -  // comm_buffer_address (64-bit physical address) > > -  CommunicateSmcArgs.Arg2 = (UINTN)mNsCommBuffMemRegion.PhysicalBase; > > +  // Use the FF-A interface if enabled. > > +  if (FixedPcdGet32 (PcdFfaEnable) != 0) { > > +    // FF-A Interface ID for direct message communication > > +    CommunicateSmcArgs.Arg0 = > ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH64; > > > > -  // comm_size_address (not used, indicated by setting to zero) > > -  CommunicateSmcArgs.Arg3 = 0; > > +    // FF-A Destination EndPoint ID, not used as of now > > +    CommunicateSmcArgs.Arg1 = mFfaPartId << 16 | mStmmPartInfo.PartId; > > > > +    // Reserved for future use(MBZ) > > +    CommunicateSmcArgs.Arg2 = 0x0; > > + > > +    // comm_buffer_address (64-bit physical address) > > +    CommunicateSmcArgs.Arg3 = (UINTN)mNsCommBuffMemRegion.PhysicalBase; > > + > > +    // Cookie > > +    CommunicateSmcArgs.Arg4 = 0x0; > > + > > +    // Not Used > > +    CommunicateSmcArgs.Arg5 = 0; > > + > > +    // comm_size_address (not used, indicated by setting to zero) > > +    CommunicateSmcArgs.Arg6 = 0; > > +  } else { > > +    // SMC Function ID > > +    CommunicateSmcArgs.Arg0 = ARM_SMC_ID_MM_COMMUNICATE_AARCH64; > > + > > +    // Cookie > > +    CommunicateSmcArgs.Arg1 = 0; > > + > > +    // comm_buffer_address (64-bit physical address) > > +    CommunicateSmcArgs.Arg2 = (UINTN)mNsCommBuffMemRegion.PhysicalBase; > > + > > +    // comm_size_address (not used, indicated by setting to zero) > > +    CommunicateSmcArgs.Arg3 = 0; > > +  } > > + > > +ffa_intr_loop: > >     // Call the Standalone MM environment. > >     ArmCallSmc (&CommunicateSmcArgs); > > > > -  switch (CommunicateSmcArgs.Arg0) { > > -    case ARM_SMC_MM_RET_SUCCESS: > > -      ZeroMem (CommBufferVirtual, BufferSize); > > -      // On successful return, the size of data being returned is > inferred from > > -      // MessageLength + Header. > > -      CommunicateHeader = (EFI_MM_COMMUNICATE_HEADER > *)mNsCommBuffMemRegion.VirtualBase; > > -      BufferSize        = CommunicateHeader->MessageLength + > > -                          sizeof (CommunicateHeader->HeaderGuid) + > > -                          sizeof (CommunicateHeader->MessageLength); > > - > > -      CopyMem ( > > -        CommBufferVirtual, > > -        (VOID *)mNsCommBuffMemRegion.VirtualBase, > > -        BufferSize > > -        ); > > -      Status = EFI_SUCCESS; > > -      break; > > - > > -    case ARM_SMC_MM_RET_INVALID_PARAMS: > > -      Status = EFI_INVALID_PARAMETER; > > -      break; > > - > > -    case ARM_SMC_MM_RET_DENIED: > > -      Status = EFI_ACCESS_DENIED; > > -      break; > > - > > -    case ARM_SMC_MM_RET_NO_MEMORY: > > -      // Unexpected error since the CommSize was checked for zero > length > > -      // prior to issuing the SMC > > -      Status = EFI_OUT_OF_RESOURCES; > > -      ASSERT (0); > > -      break; > > - > > -    default: > > -      Status = EFI_ACCESS_DENIED; > > -      ASSERT (0); > > +  Ret = CommunicateSmcArgs.Arg0; > > + > > +  if (FixedPcdGet32 (PcdFfaEnable) != 0) { > > +    if (Ret == ARM_SVC_ID_FFA_INTERRUPT_AARCH32) { > > +      DEBUG ((DEBUG_INFO, "Resuming interrupted FF-A call \n")); > > + > > +      // FF-A Interface ID for running the interrupted partition > > +      CommunicateSmcArgs.Arg0 = ARM_SVC_ID_FFA_RUN_AARCH32; > > + > > +      // FF-A Destination EndPoint and vCPU ID, TODO: We are > assuming vCPU0 of the > > +      // StMM SP since it is UP. > > +      CommunicateSmcArgs.Arg1 = mStmmPartInfo.PartId << 16; > > + > > +      // Loop if the call was interrupted > > +      goto ffa_intr_loop; > > +    } > > +  } > > + > > +  if (((FixedPcdGet32 (PcdFfaEnable) != 0) && > > +      (Ret == ARM_SVC_ID_FFA_MSG_SEND_DIRECT_RESP)) || > > +      (Ret == ARM_SMC_MM_RET_SUCCESS)) { > > +    ZeroMem (CommBufferVirtual, BufferSize); > > +    // On successful return, the size of data being returned is > inferred from > > +    // MessageLength + Header. > > +    CommunicateHeader = (EFI_MM_COMMUNICATE_HEADER > *)mNsCommBuffMemRegion.VirtualBase; > > +    BufferSize = CommunicateHeader->MessageLength + > > +                 sizeof (CommunicateHeader->HeaderGuid) + > > +                 sizeof (CommunicateHeader->MessageLength); > > + > > +    CopyMem (CommBufferVirtual, (VOID > *)mNsCommBuffMemRegion.VirtualBase, > > +             BufferSize); > > +    Status = EFI_SUCCESS; > > +    return Status; > > +  } > > + > > +  if (FixedPcdGet32 (PcdFfaEnable) != 0) { > > +    Ret = CommunicateSmcArgs.Arg2; > > +  } > > + > > +  // Error Codes are same for FF-A and SMC interface > > +  switch (Ret) { > > +  case ARM_SMC_MM_RET_INVALID_PARAMS: > > +    Status = EFI_INVALID_PARAMETER; > > +    break; > > + > > +  case ARM_SMC_MM_RET_DENIED: > > +    Status = EFI_ACCESS_DENIED; > > +    break; > > + > > +  case ARM_SMC_MM_RET_NO_MEMORY: > > +    // Unexpected error since the CommSize was checked for zero length > > +    // prior to issuing the SMC > > +    Status = EFI_OUT_OF_RESOURCES; > > +    ASSERT (0); > > +    break; > > + > > +  default: > > +    Status = EFI_ACCESS_DENIED; > > +    ASSERT (0); > >     } > > > >     return Status; --------------phtGgUN5Qovo0kIPQ8G1KL00 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi Achin,

The main MM communicate usage in PEI we have today is the variable service,
because non secure UEFI cannot access flash directly.


We had a few use cases where we need to check the variable from the previous

boot in PEI, update some configuration data and consume it for the rest of the
boot. I think it will break as is if we switch over to FFA aware framework?


Please let me know how you think about the potential support in PEI.

Regards,
Kun

On 7/12/2023 7:21 AM, Achin Gupta wrote:
Hi Kun,

IIUC, not much happens during the PEI phase on Arm platforms. Hence the patches focus on DXE in the Normal world. It would be difficult to provide an effort estimate as we do not see a use case and consequently this is not on the to-do list. Would you be able to provide more detail about the scenarios you have in mind?

cheers,
Achin
From: Kun Qin <kuqin12@gmail.com>
Sent: 11 July 2023 20:22
To: devel@edk2.groups.io <devel@edk2.groups.io>; Nishant Sharma <Nishant.Sharma@arm.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>; Sami Mujawar <Sami.Mujawar@arm.com>; Thomas Abraham <thomas.abraham@arm.com>; Sayanta Pattanayak <Sayanta.Pattanayak@arm.com>; Achin Gupta <Achin.Gupta@arm.com>; Aditya Angadi <Aditya.Angadi@arm.com>
Subject: Re: [edk2-devel] [edk2-platforms][PATCH V1 19/20] ArmPkg/MmCommunicationDxe: Use the FF-A transport for MM requests
 
Hi Nishant,

Thank you for sending out the patch. Can you please evaluate how much
effort it would be
to support the same for MmCommunicatePei? I think it would provide
better coverage for
the FFA support if we can have that change.

Thanks,
Kun

On 7/11/2023 7:36 AM, Nishant Sharma wrote:
> From: Achin Gupta <achin.gupta@arm.com>
>
> This patch packages requests for accessing a Standalone MM driver
> through the MM communication protocol as FF-A direct messages.
> Corresponding changes in Standalone MM Core ensure that responses are
> packaged in the same way.
>
> Signed-off-by: Achin Gupta <achin.gupta@arm.com>
> Co-developed-by: Aditya Angadi <aditya.angadi@arm.com>
> Signed-off-by: Nishant Sharma <nishant.sharma@arm.com>
> ---
>   ArmPkg/Include/IndustryStandard/ArmFfaSvc.h         |   2 +
>   ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c | 141 +++++++++++++-------
>   2 files changed, 97 insertions(+), 46 deletions(-)
>
> diff --git a/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h b/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h
> index 530af8bd3c2e..493997346143 100644
> --- a/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h
> +++ b/ArmPkg/Include/IndustryStandard/ArmFfaSvc.h
> @@ -23,6 +23,7 @@
>   #define ARM_SVC_ID_FFA_RXTX_UNMAP_AARCH32            0x84000067
>   #define ARM_SVC_ID_FFA_PARTITION_INFO_GET_AARCH32    0x84000068
>   #define ARM_SVC_ID_FFA_ID_GET_AARCH32                0x84000069
> +#define ARM_SVC_ID_FFA_RUN_AARCH32                   0x8400006D
>   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH32   0x8400006F
>   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_RESP_AARCH32  0x84000070
>   #define ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH64   0xC400006F
> @@ -31,6 +32,7 @@
>   #define ARM_SVC_ID_FFA_SUCCESS_AARCH64               0xC4000061
>   #define ARM_SVC_ID_FFA_MEM_PERM_SET_AARCH32          0x84000089
>   #define ARM_SVC_ID_FFA_MEM_PERM_GET_AARCH32          0x84000088
> +#define ARM_SVC_ID_FFA_INTERRUPT_AARCH32             0x84000062
>   #define ARM_SVC_ID_FFA_ERROR_AARCH32                 0x84000060
>   #define ARM_SVC_ID_FFA_ERROR_AARCH64                 0xC4000060
>   #define ARM_SVC_ID_FFA_MSG_WAIT_AARCH32              0x8400006B
> diff --git a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> index 94a5d96c051d..a70318581bd2 100644
> --- a/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> +++ b/ArmPkg/Drivers/MmCommunicationDxe/MmCommunication.c
> @@ -100,6 +100,7 @@ MmCommunication2Communicate (
>     ARM_SMC_ARGS               CommunicateSmcArgs;
>     EFI_STATUS                 Status;
>     UINTN                      BufferSize;
> +  UINTN                      Ret;
>  
>     Status     = EFI_ACCESS_DENIED;
>     BufferSize = 0;
> @@ -160,60 +161,108 @@ MmCommunication2Communicate (
>       return Status;
>     }
>  
> -  // SMC Function ID
> -  CommunicateSmcArgs.Arg0 = ARM_SMC_ID_MM_COMMUNICATE_AARCH64;
> -
> -  // Cookie
> -  CommunicateSmcArgs.Arg1 = 0;
> -
>     // Copy Communication Payload
>     CopyMem ((VOID *)mNsCommBuffMemRegion.VirtualBase, CommBufferVirtual, BufferSize);
>  
> -  // comm_buffer_address (64-bit physical address)
> -  CommunicateSmcArgs.Arg2 = (UINTN)mNsCommBuffMemRegion.PhysicalBase;
> +  // Use the FF-A interface if enabled.
> +  if (FixedPcdGet32 (PcdFfaEnable) != 0) {
> +    // FF-A Interface ID for direct message communication
> +    CommunicateSmcArgs.Arg0 = ARM_SVC_ID_FFA_MSG_SEND_DIRECT_REQ_AARCH64;
>  
> -  // comm_size_address (not used, indicated by setting to zero)
> -  CommunicateSmcArgs.Arg3 = 0;
> +    // FF-A Destination EndPoint ID, not used as of now
> +    CommunicateSmcArgs.Arg1 = mFfaPartId << 16 | mStmmPartInfo.PartId;
>  
> +    // Reserved for future use(MBZ)
> +    CommunicateSmcArgs.Arg2 = 0x0;
> +
> +    // comm_buffer_address (64-bit physical address)
> +    CommunicateSmcArgs.Arg3 = (UINTN)mNsCommBuffMemRegion.PhysicalBase;
> +
> +    // Cookie
> +    CommunicateSmcArgs.Arg4 = 0x0;
> +
> +    // Not Used
> +    CommunicateSmcArgs.Arg5 = 0;
> +
> +    // comm_size_address (not used, indicated by setting to zero)
> +    CommunicateSmcArgs.Arg6 = 0;
> +  } else {
> +    // SMC Function ID
> +    CommunicateSmcArgs.Arg0 = ARM_SMC_ID_MM_COMMUNICATE_AARCH64;
> +
> +    // Cookie
> +    CommunicateSmcArgs.Arg1 = 0;
> +
> +    // comm_buffer_address (64-bit physical address)
> +    CommunicateSmcArgs.Arg2 = (UINTN)mNsCommBuffMemRegion.PhysicalBase;
> +
> +    // comm_size_address (not used, indicated by setting to zero)
> +    CommunicateSmcArgs.Arg3 = 0;
> +  }
> +
> +ffa_intr_loop:
>     // Call the Standalone MM environment.
>     ArmCallSmc (&CommunicateSmcArgs);
>  
> -  switch (CommunicateSmcArgs.Arg0) {
> -    case ARM_SMC_MM_RET_SUCCESS:
> -      ZeroMem (CommBufferVirtual, BufferSize);
> -      // On successful return, the size of data being returned is inferred from
> -      // MessageLength + Header.
> -      CommunicateHeader = (EFI_MM_COMMUNICATE_HEADER *)mNsCommBuffMemRegion.VirtualBase;
> -      BufferSize        = CommunicateHeader->MessageLength +
> -                          sizeof (CommunicateHeader->HeaderGuid) +
> -                          sizeof (CommunicateHeader->MessageLength);
> -
> -      CopyMem (
> -        CommBufferVirtual,
> -        (VOID *)mNsCommBuffMemRegion.VirtualBase,
> -        BufferSize
> -        );
> -      Status = EFI_SUCCESS;
> -      break;
> -
> -    case ARM_SMC_MM_RET_INVALID_PARAMS:
> -      Status = EFI_INVALID_PARAMETER;
> -      break;
> -
> -    case ARM_SMC_MM_RET_DENIED:
> -      Status = EFI_ACCESS_DENIED;
> -      break;
> -
> -    case ARM_SMC_MM_RET_NO_MEMORY:
> -      // Unexpected error since the CommSize was checked for zero length
> -      // prior to issuing the SMC
> -      Status = EFI_OUT_OF_RESOURCES;
> -      ASSERT (0);
> -      break;
> -
> -    default:
> -      Status = EFI_ACCESS_DENIED;
> -      ASSERT (0);
> +  Ret = CommunicateSmcArgs.Arg0;
> +
> +  if (FixedPcdGet32 (PcdFfaEnable) != 0) {
> +    if (Ret == ARM_SVC_ID_FFA_INTERRUPT_AARCH32) {
> +      DEBUG ((DEBUG_INFO, "Resuming interrupted FF-A call \n"));
> +
> +      // FF-A Interface ID for running the interrupted partition
> +      CommunicateSmcArgs.Arg0 = ARM_SVC_ID_FFA_RUN_AARCH32;
> +
> +      // FF-A Destination EndPoint and vCPU ID, TODO: We are assuming vCPU0 of the
> +      // StMM SP since it is UP.
> +      CommunicateSmcArgs.Arg1 = mStmmPartInfo.PartId << 16;
> +
> +      // Loop if the call was interrupted
> +      goto ffa_intr_loop;
> +    }
> +  }
> +
> +  if (((FixedPcdGet32 (PcdFfaEnable) != 0) &&
> +      (Ret == ARM_SVC_ID_FFA_MSG_SEND_DIRECT_RESP)) ||
> +      (Ret == ARM_SMC_MM_RET_SUCCESS)) {
> +    ZeroMem (CommBufferVirtual, BufferSize);
> +    // On successful return, the size of data being returned is inferred from
> +    // MessageLength + Header.
> +    CommunicateHeader = (EFI_MM_COMMUNICATE_HEADER *)mNsCommBuffMemRegion.VirtualBase;
> +    BufferSize = CommunicateHeader->MessageLength +
> +                 sizeof (CommunicateHeader->HeaderGuid) +
> +                 sizeof (CommunicateHeader->MessageLength);
> +
> +    CopyMem (CommBufferVirtual, (VOID *)mNsCommBuffMemRegion.VirtualBase,
> +             BufferSize);
> +    Status = EFI_SUCCESS;
> +    return Status;
> +  }
> +
> +  if (FixedPcdGet32 (PcdFfaEnable) != 0) {
> +    Ret = CommunicateSmcArgs.Arg2;
> +  }
> +
> +  // Error Codes are same for FF-A and SMC interface
> +  switch (Ret) {
> +  case ARM_SMC_MM_RET_INVALID_PARAMS:
> +    Status = EFI_INVALID_PARAMETER;
> +    break;
> +
> +  case ARM_SMC_MM_RET_DENIED:
> +    Status = EFI_ACCESS_DENIED;
> +    break;
> +
> +  case ARM_SMC_MM_RET_NO_MEMORY:
> +    // Unexpected error since the CommSize was checked for zero length
> +    // prior to issuing the SMC
> +    Status = EFI_OUT_OF_RESOURCES;
> +    ASSERT (0);
> +    break;
> +
> +  default:
> +    Status = EFI_ACCESS_DENIED;
> +    ASSERT (0);
>     }
>  
>     return Status;
--------------phtGgUN5Qovo0kIPQ8G1KL00--