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: "Dong, Eric" <eric.dong@intel.com>
Subject: Re: [Patch] MdeModulePkg/Core/Dxe: Remove extra connects for UEFI Applications
Date: Thu, 9 Nov 2017 17:41:50 +0000	[thread overview]
Message-ID: <E92EE9817A31E24EB0585FDF735412F5A7DBEBB1@ORSMSX113.amr.corp.intel.com> (raw)
In-Reply-To: <0C09AFA07DD0434D9E2A0C6AEB0483103B9B3AB7@shsmsx102.ccr.corp.intel.com>

Star,

Thanks for noticing the inconsistency.

I agree that Image->Type is a better choice.

Mike

> -----Original Message-----
> From: Zeng, Star
> Sent: Thursday, November 9, 2017 5:10 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>;
> edk2-devel@lists.01.org
> Cc: Dong, Eric <eric.dong@intel.com>; Zeng, Star
> <star.zeng@intel.com>
> Subject: RE: [Patch] MdeModulePkg/Core/Dxe: Remove
> extra connects for UEFI Applications
> 
> Reviewed-by: Star Zeng <star.zeng@intel.com>
> 
> BTW: I see the code is using Image-
> >ImageContext.ImageType at some places and Image->Type
> at other place, it seems a little inconsistent.
> 
> Thanks,
> Star
> -----Original Message-----
> From: Kinney, Michael D
> Sent: Thursday, November 9, 2017 1:55 AM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Dong, Eric
> <eric.dong@intel.com>
> Subject: [Patch] MdeModulePkg/Core/Dxe: Remove extra
> connects for UEFI Applications
> 
> https://bugzilla.tianocore.org/show_bug.cgi?id=765
> 
> The UEFI Specification Boot Services chapter,
> StartImage() service,
> EFF 1.10 Extension requires extra calls to
> ConnectController()
> if a UEFI Driver produces handles. The DXE Core is
> performing these
> extra calls to ConnectController() without evaluating
> the ImageType.
> 
> A filter is added to not make extra calls to
> ConnectController()
> if the ImageType is
> EFI_IMAGE_SUBSYSTEM_EFI_APPLICATION.
> 
> Without this filter, extra calls to ConnectController()
> may be
> performed by UEFI Applications or a UEFI Shell
> Applications that
> also call ConnectController().
> 
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Michael D Kinney
> <michael.d.kinney@intel.com>
> ---
>  MdeModulePkg/Core/Dxe/Image/Image.c | 12 ++++++++++--
>  1 file changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/MdeModulePkg/Core/Dxe/Image/Image.c
> b/MdeModulePkg/Core/Dxe/Image/Image.c
> index 4e22aa6dc7..c6b8ff44b9 100644
> --- a/MdeModulePkg/Core/Dxe/Image/Image.c
> +++ b/MdeModulePkg/Core/Dxe/Image/Image.c
> @@ -1703,9 +1703,17 @@ CoreStartImage (
>    mCurrentImage = LastImage;
> 
>    //
> -  // Go connect any handles that were created or
> modified while the image executed.
> +  // UEFI Specification - StartImage() - EFI 1.10
> Extension
> +  // To maintain compatibility with UEFI drivers that
> are written to the EFI
> +  // 1.02 Specification, StartImage() must monitor the
> handle database before
> +  // and after each image is started. If any handles
> are created or modified
> +  // when an image is started, then
> EFI_BOOT_SERVICES.ConnectController() must
> +  // be called with the Recursive parameter set to
> TRUE for each of the newly
> +  // created or modified handles before StartImage()
> returns.
>    //
> -  CoreConnectHandlesByKey (HandleDatabaseKey);
> +  if (Image->ImageContext.ImageType !=
> EFI_IMAGE_SUBSYSTEM_EFI_APPLICATION) {
> +    CoreConnectHandlesByKey (HandleDatabaseKey);
> +  }
> 
>    //
>    // Handle the image's returned ExitData
> --
> 2.14.2.windows.3



      reply	other threads:[~2017-11-09 17:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 17:54 [Patch] MdeModulePkg/Core/Dxe: Remove extra connects for UEFI Applications Michael D Kinney
2017-11-09 13:09 ` Zeng, Star
2017-11-09 17:41   ` Kinney, Michael D [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=E92EE9817A31E24EB0585FDF735412F5A7DBEBB1@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