public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Kinney, Michael D" <michael.d.kinney@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [Patch 1/1] MdePkg/UefiLib: Add EfiLocateProtocolBuffer()
Date: Thu, 1 Feb 2018 02:06:36 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5B895C52D@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103BA1DD67@shsmsx102.ccr.corp.intel.com>

Star,

I agree with your observation.  And the API specifically says
that EFI_BOOT_SERVICES.AllocatePool() is used, so I agree with
your suggested change.

However, there are other APIs in the UefiLib implementation
that use the MemoryAllocationLib services.  Should those be 
updated too?

Mike

> -----Original Message-----
> From: Zeng, Star
> Sent: Wednesday, January 31, 2018 5:32 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-
> devel@lists.01.org
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Yao,
> Jiewen <jiewen.yao@intel.com>; Gao, Liming
> <liming.gao@intel.com>; Zeng, Star <star.zeng@intel.com>
> Subject: RE: [edk2] [Patch 1/1] MdePkg/UefiLib: Add
> EfiLocateProtocolBuffer()
> 
> Hi Mike,
> 
> UefiLib is capable to be used by SMM Core or SMM driver
> before SmmReadyToLock.
> 
> And the new interface has the comment below.
> 
> +                            The returned buffer is
> allocated using
> +
> EFI_BOOT_SERVICES.AllocatePool().  The caller is
> +                            responsible for freeing this
> buffer with
> +
> EFI_BOOT_SERVICES.FreePool().
> 
> But the implementation is using AllocateZeroPool() like
> below, that will direct to gSmst->AllocatePool for SMM
> Core or SMM driver.
> 
> +  //
> +  // Allocate array of protocol instances
> +  //
> +  *Buffer = AllocateZeroPool (NoHandles * sizeof (VOID
> *));
> +  if (*Buffer == NULL) {
> +    return EFI_OUT_OF_RESOURCES;
> +  }
> 
> Should the implementation use gBS->AllocatePool() +
> ZeroMem() instead of AllocateZeroPool()?
> 
> 
> Thanks,
> Star
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org]
> On Behalf Of Kinney, Michael D
> Sent: Thursday, February 1, 2018 7:33 AM
> To: edk2-devel@lists.01.org
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Yao,
> Jiewen <jiewen.yao@intel.com>; Gao, Liming
> <liming.gao@intel.com>
> Subject: [edk2] [Patch 1/1] MdePkg/UefiLib: Add
> EfiLocateProtocolBuffer()
> 
> From: Michael D Kinney <michael.d.kinney@intel.com>
> 
> https://bugzilla.tianocore.org/show_bug.cgi?id=838
> 
> Add new API to the UefiLib that locates and returns
> an array of protocols instances that match a given
> protocol.
> 
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Michael D Kinney
> <michael.d.kinney@intel.com>
> ---
>  MdePkg/Include/Library/UefiLib.h |  32 +++++++++++-
>  MdePkg/Library/UefiLib/UefiLib.c | 107
> ++++++++++++++++++++++++++++++++++++++-
>  2 files changed, 137 insertions(+), 2 deletions(-)
> 
> diff --git a/MdePkg/Include/Library/UefiLib.h
> b/MdePkg/Include/Library/UefiLib.h
> index 0b14792a0a..54bc2cc5a3 100644
> --- a/MdePkg/Include/Library/UefiLib.h
> +++ b/MdePkg/Include/Library/UefiLib.h
> @@ -12,7 +12,7 @@
>    of size reduction when compiler optimization is
> disabled. If MDEPKG_NDEBUG is
>    defined, then debug and assert related macros wrapped
> by it are the NULL implementations.
> 
> -Copyright (c) 2006 - 2017, Intel Corporation. All rights
> reserved.<BR>
> +Copyright (c) 2006 - 2018, Intel Corporation. All rights
> reserved.<BR>
>  This program and the accompanying materials are licensed
> and made available under
>  the terms and conditions of the BSD License that
> accompanies this distribution.
>  The full text of the license may be found at
> @@ -1490,4 +1490,34 @@ CatSPrint (
>    ...
>    );
> 
> +/**
> +  Returns an array of protocol instance that matches the
> given protocol.
> +
> +  @param[in]  Protocol      Provides the protocol to
> search for.
> +  @param[out] NoProtocols   The number of protocols
> returned in Buffer.
> +  @param[out] Buffer        A pointer to the buffer to
> return the requested
> +                            array of protocol instances
> that match Protocol.
> +                            The returned buffer is
> allocated using
> +
> EFI_BOOT_SERVICES.AllocatePool().  The caller is
> +                            responsible for freeing this
> buffer with
> +
> EFI_BOOT_SERVICES.FreePool().
> +
> +  @retval EFI_SUCCESS            The array of protocols
> was returned in Buffer,
> +                                 and the number of
> protocols in Buffer was
> +                                 returned in
> NoProtocols.
> +  @retval EFI_NOT_FOUND          No protocols found.
> +  @retval EFI_OUT_OF_RESOURCES   There is not enough
> pool memory to store the
> +                                 matching results.
> +  @retval EFI_INVALID_PARAMETER  Protocol is NULL.
> +  @retval EFI_INVALID_PARAMETER  NoProtocols is NULL.
> +  @retval EFI_INVALID_PARAMETER  Buffer is NULL.
> +
> +**/
> +EFI_STATUS
> +EFIAPI
> +EfiLocateProtocolBuffer (
> +  IN  EFI_GUID  *Protocol,
> +  OUT UINTN     *NoProtocols,
> +  OUT VOID      ***Buffer
> +  );
>  #endif
> diff --git a/MdePkg/Library/UefiLib/UefiLib.c
> b/MdePkg/Library/UefiLib/UefiLib.c
> index a7eee01240..d86db4bd67 100644
> --- a/MdePkg/Library/UefiLib/UefiLib.c
> +++ b/MdePkg/Library/UefiLib/UefiLib.c
> @@ -5,7 +5,7 @@
>    EFI Driver Model related protocols, manage Unicode
> string tables for UEFI Drivers,
>    and print messages on the console output and standard
> error devices.
> 
> -  Copyright (c) 2006 - 2017, Intel Corporation. All
> rights reserved.<BR>
> +  Copyright (c) 2006 - 2018, Intel Corporation. All
> rights reserved.<BR>
>    This program and the accompanying materials
>    are licensed and made available under the terms and
> conditions of the BSD License
>    which accompanies this distribution.  The full text of
> the license may be found at
> @@ -1605,3 +1605,108 @@ GetBestLanguage (
>    //
>    return NULL;
>  }
> +
> +/**
> +  Returns an array of protocol instance that matches the
> given protocol.
> +
> +  @param[in]  Protocol      Provides the protocol to
> search for.
> +  @param[out] NoProtocols   The number of protocols
> returned in Buffer.
> +  @param[out] Buffer        A pointer to the buffer to
> return the requested
> +                            array of protocol instances
> that match Protocol.
> +                            The returned buffer is
> allocated using
> +
> EFI_BOOT_SERVICES.AllocatePool().  The caller is
> +                            responsible for freeing this
> buffer with
> +
> EFI_BOOT_SERVICES.FreePool().
> +
> +  @retval EFI_SUCCESS            The array of protocols
> was returned in Buffer,
> +                                 and the number of
> protocols in Buffer was
> +                                 returned in
> NoProtocols.
> +  @retval EFI_NOT_FOUND          No protocols found.
> +  @retval EFI_OUT_OF_RESOURCES   There is not enough
> pool memory to store the
> +                                 matching results.
> +  @retval EFI_INVALID_PARAMETER  Protocol is NULL.
> +  @retval EFI_INVALID_PARAMETER  NoProtocols is NULL.
> +  @retval EFI_INVALID_PARAMETER  Buffer is NULL.
> +
> +**/
> +EFI_STATUS
> +EFIAPI
> +EfiLocateProtocolBuffer (
> +  IN  EFI_GUID  *Protocol,
> +  OUT UINTN     *NoProtocols,
> +  OUT VOID      ***Buffer
> +  )
> +{
> +  EFI_STATUS  Status;
> +  UINTN       NoHandles;
> +  EFI_HANDLE  *HandleBuffer;
> +  UINTN       Index;
> +
> +  //
> +  // Check input parameters
> +  //
> +  if (Protocol == NULL || NoProtocols == NULL || Buffer
> == NULL) {
> +    return EFI_INVALID_PARAMETER;
> +  }
> +
> +  //
> +  // Initialze output parameters
> +  //
> +  *NoProtocols = 0;
> +  *Buffer = NULL;
> +
> +  //
> +  // Retrieve the array of handles that support Protocol
> +  //
> +  Status = gBS->LocateHandleBuffer (
> +                  ByProtocol,
> +                  Protocol,
> +                  NULL,
> +                  &NoHandles,
> +                  &HandleBuffer
> +                  );
> +  if (EFI_ERROR (Status)) {
> +    return Status;
> +  }
> +
> +  //
> +  // Allocate array of protocol instances
> +  //
> +  *Buffer = AllocateZeroPool (NoHandles * sizeof (VOID
> *));
> +  if (*Buffer == NULL) {
> +    return EFI_OUT_OF_RESOURCES;
> +  }
> +
> +  //
> +  // Lookup Protocol on each handle in HandleBuffer to
> fill in the array of
> +  // protocol instances.  Handle case where protocol
> instance was present when
> +  // LocateHandleBuffer() was called, but is not present
> when HandleProtocol()
> +  // is called.
> +  //
> +  for (Index = 0, *NoProtocols = 0; Index < NoHandles;
> Index++) {
> +    Status = gBS->HandleProtocol (
> +                    HandleBuffer[Index],
> +                    Protocol,
> +                    &((*Buffer)[*NoProtocols])
> +                    );
> +    if (!EFI_ERROR (Status)) {
> +      (*NoProtocols)++;
> +    }
> +  }
> +
> +  //
> +  // Free the handle buffer
> +  //
> +  FreePool (HandleBuffer);
> +
> +  //
> +  // Make sure at least one protocol instance was found
> +  //
> +  if (*NoProtocols == 0) {
> +    FreePool (*Buffer);
> +    *Buffer = NULL;
> +    return EFI_NOT_FOUND;
> +  }
> +
> +  return EFI_SUCCESS;
> +}
> --
> 2.14.2.windows.3
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-02-01  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 23:33 [Patch 0/1] MdePkg/UefiLib: Add EfiLocateProtocolBuffer() Kinney, Michael D
2018-01-31 23:33 ` [Patch 1/1] " Kinney, Michael D
2018-02-01  1:31   ` Zeng, Star
2018-02-01  2:06     ` Kinney, Michael D [this message]
2018-02-01  2:20       ` Zeng, Star
2018-02-01  1:19 ` [Patch 0/1] " Gao, Liming
2018-02-01  1:47   ` Kinney, Michael D

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=E92EE9817A31E24EB0585FDF735412F5B895C52D@ORSMSX113.amr.corp.intel.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