public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Nate DeSimone" <nathaniel.l.desimone@intel.com>
To: "Chiu, Chasel" <chasel.chiu@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH] IntelFsp2Pkg: FSP should support input UPD as NULL.
Date: Tue, 25 Oct 2022 00:08:47 +0000	[thread overview]
Message-ID: <MW4PR11MB5821E2171CBF313EF10E79E9CD319@MW4PR11MB5821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221024040511.2081-1-chasel.chiu@intel.com>

Reviewed-by: Nate DeSimone <nathaniel.l.desimone@intel.com>

-----Original Message-----
From: Chiu, Chasel <chasel.chiu@intel.com> 
Sent: Sunday, October 23, 2022 9:05 PM
To: devel@edk2.groups.io
Cc: Chiu, Chasel <chasel.chiu@intel.com>; Desimone, Nathaniel L <nathaniel.l.desimone@intel.com>; Zeng, Star <star.zeng@intel.com>
Subject: [PATCH] IntelFsp2Pkg: FSP should support input UPD as NULL.

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=4114
FSP specification supports input UPD as NULL cases which FSP will use built-in UPD region instead.
FSP should not return INVALID_PARAMETER in such cases.

Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
Cc: Star Zeng <star.zeng@intel.com>
Signed-off-by: Chasel Chiu <chasel.chiu@intel.com>
---
 IntelFsp2Pkg/FspSecCore/SecFspApiChk.c         | 11 +++++++++--
 IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryT.nasm |  8 --------  IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm  |  7 -------
 3 files changed, 9 insertions(+), 17 deletions(-)

diff --git a/IntelFsp2Pkg/FspSecCore/SecFspApiChk.c b/IntelFsp2Pkg/FspSecCore/SecFspApiChk.c
index a44fbf2a50..bfbdf70083 100644
--- a/IntelFsp2Pkg/FspSecCore/SecFspApiChk.c
+++ b/IntelFsp2Pkg/FspSecCore/SecFspApiChk.c
@@ -44,6 +44,8 @@ FspApiCallingCheck (
     //     if (((UINTN)FspData != MAX_ADDRESS) && ((UINTN)FspData != MAX_UINT32)) {       Status = EFI_UNSUPPORTED;+    } else if (ApiParam == NULL) {+      Status = EFI_SUCCESS;     } else if (EFI_ERROR (FspUpdSignatureCheck (ApiIdx, ApiParam))) {       Status = EFI_INVALID_PARAMETER;     }@@ -67,9 +69,12 @@ FspApiCallingCheck (
     } else {       if (FspData->Signature != FSP_GLOBAL_DATA_SIGNATURE) {         Status = EFI_UNSUPPORTED;-      } else if (EFI_ERROR (FspUpdSignatureCheck (FspSiliconInitApiIndex, ApiParam))) {-        Status = EFI_INVALID_PARAMETER;       } else if (ApiIdx == FspSiliconInitApiIndex) {+        if (ApiParam == NULL) {+          Status = EFI_SUCCESS;+        } else if (EFI_ERROR (FspUpdSignatureCheck (FspSiliconInitApiIndex, ApiParam))) {+          Status = EFI_INVALID_PARAMETER;+        }         //         // Reset MultiPhase NumberOfPhases to zero         //@@ -89,6 +94,8 @@ FspApiCallingCheck (
     } else {       if (FspData->Signature != FSP_GLOBAL_DATA_SIGNATURE) {         Status = EFI_UNSUPPORTED;+      } else if (ApiParam == NULL) {+        Status = EFI_SUCCESS;       } else if (EFI_ERROR (FspUpdSignatureCheck (FspSmmInitApiIndex, ApiParam))) {         Status = EFI_INVALID_PARAMETER;       }diff --git a/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryT.nasm b/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryT.nasm
index 61030a843b..52e1ff6f1f 100644
--- a/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryT.nasm
+++ b/IntelFsp2Pkg/FspSecCore/Ia32/FspApiEntryT.nasm
@@ -555,14 +555,6 @@ ASM_PFX(TempRamInitApi):
   SAVE_EAX   SAVE_EDX -  ;-  ; Check Parameter-  ;-  mov       eax, dword [esp + 4]-  cmp       eax, 0-  mov       eax, 80000002h-  jz        TempRamInitExit-   ;   ; Sec Platform Init   ;diff --git a/IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm b/IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm
index 7dd89c531a..23bb2b0481 100644
--- a/IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm
+++ b/IntelFsp2Pkg/FspSecCore/X64/FspApiEntryT.nasm
@@ -441,13 +441,6 @@ ASM_PFX(TempRamInitApi):
   or        rax, rdx   SAVE_TS   rax -  ;-  ; Check Parameter-  ;-  cmp       rcx, 0-  mov       rcx, 08000000000000002h-  jz        TempRamInitExit-   ;   ; Sec Platform Init   ;-- 
2.35.0.windows.1


      reply	other threads:[~2022-10-25  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  4:05 [PATCH] IntelFsp2Pkg: FSP should support input UPD as NULL Chiu, Chasel
2022-10-25  0:08 ` Nate DeSimone [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-list 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=MW4PR11MB5821E2171CBF313EF10E79E9CD319@MW4PR11MB5821.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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