From: Achin Gupta <Achin.Gupta@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Jagadeesh Ujja <Jagadeesh.Ujja@arm.com>, nd <nd@arm.com>
Subject: Re: [PATCH 07/10] StandaloneMmPkg/Core: dispatch all drivers at init time
Date: Wed, 6 Mar 2019 16:56:56 +0000 [thread overview]
Message-ID: <20190306165648.GT21602@mac-ubuntu-vm> (raw)
In-Reply-To: <20190305133248.4828-8-ard.biesheuvel@linaro.org>
Reviewed-by: achin.gupta@arm.com
On Tue, Mar 05, 2019 at 02:32:45PM +0100, Ard Biesheuvel wrote:
> Instead of deferring dispatch of the remaining MM drivers once the
> CPU driver has been dispatched, proceed and dispatch all drivers.
> This makes sense for standalone MM, since all dispatchable drivers
> should be present in the initial firmware volume anyway: dispatch
> of additional FVs originating in the non-secure side is not supported.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> StandaloneMmPkg/Core/Dispatcher.c | 92 --------------------
> StandaloneMmPkg/Core/StandaloneMmCore.c | 1 -
> 2 files changed, 93 deletions(-)
>
> diff --git a/StandaloneMmPkg/Core/Dispatcher.c b/StandaloneMmPkg/Core/Dispatcher.c
> index 8a2ad5118d92..bede4832cfb7 100644
> --- a/StandaloneMmPkg/Core/Dispatcher.c
> +++ b/StandaloneMmPkg/Core/Dispatcher.c
> @@ -575,7 +575,6 @@ MmDispatcher (
> LIST_ENTRY *Link;
> EFI_MM_DRIVER_ENTRY *DriverEntry;
> BOOLEAN ReadyToRun;
> - BOOLEAN PreviousMmEntryPointRegistered;
>
> DEBUG ((DEBUG_INFO, "MmDispatcher\n"));
>
> @@ -639,11 +638,6 @@ MmDispatcher (
> DriverEntry->Initialized = TRUE;
> RemoveEntryList (&DriverEntry->ScheduledLink);
>
> - //
> - // Cache state of MmEntryPointRegistered before calling entry point
> - //
> - PreviousMmEntryPointRegistered = gMmCorePrivate->MmEntryPointRegistered;
> -
> //
> // For each MM driver, pass NULL as ImageHandle
> //
> @@ -661,20 +655,6 @@ MmDispatcher (
> DEBUG ((DEBUG_INFO, "StartImage Status - %r\n", Status));
> MmFreePages(DriverEntry->ImageBuffer, DriverEntry->NumberOfPage);
> }
> -
> - if (!PreviousMmEntryPointRegistered && gMmCorePrivate->MmEntryPointRegistered) {
> - //
> - // Return immediately if the MM Entry Point was registered by the MM
> - // Driver that was just dispatched. The MM IPL will reinvoke the MM
> - // Core Dispatcher. This is required so MM Mode may be enabled as soon
> - // as all the dependent MM Drivers for MM Mode have been dispatched.
> - // Once the MM Entry Point has been registered, then MM Mode will be
> - // used.
> - //
> - gRequestDispatch = TRUE;
> - gDispatcherRunning = FALSE;
> - return EFI_NOT_READY;
> - }
> }
>
> //
> @@ -903,78 +883,6 @@ MmAddToDriverList (
> return EFI_SUCCESS;
> }
>
> -/**
> - This function is the main entry point for an MM handler dispatch
> - or communicate-based callback.
> -
> - Event notification that is fired every time a FV dispatch protocol is added.
> - More than one protocol may have been added when this event is fired, so you
> - must loop on MmLocateHandle () to see how many protocols were added and
> - do the following to each FV:
> - If the Fv has already been processed, skip it. If the Fv has not been
> - processed then mark it as being processed, as we are about to process it.
> - Read the Fv and add any driver in the Fv to the mDiscoveredList.The
> - mDiscoveredList is never free'ed and contains variables that define
> - the other states the MM driver transitions to..
> - While you are at it read the A Priori file into memory.
> - Place drivers in the A Priori list onto the mScheduledQueue.
> -
> - @param DispatchHandle The unique handle assigned to this handler by SmiHandlerRegister().
> - @param Context Points to an optional handler context which was specified when the handler was registered.
> - @param CommBuffer A pointer to a collection of data in memory that will
> - be conveyed from a non-MM environment into an MM environment.
> - @param CommBufferSize The size of the CommBuffer.
> -
> - @return Status Code
> -
> -**/
> -EFI_STATUS
> -EFIAPI
> -MmDriverDispatchHandler (
> - IN EFI_HANDLE DispatchHandle,
> - IN CONST VOID *Context, OPTIONAL
> - IN OUT VOID *CommBuffer, OPTIONAL
> - IN OUT UINTN *CommBufferSize OPTIONAL
> - )
> -{
> - EFI_STATUS Status;
> -
> - DEBUG ((DEBUG_INFO, "MmDriverDispatchHandler\n"));
> -
> - //
> - // Execute the MM Dispatcher on any newly discovered FVs and previously
> - // discovered MM drivers that have been discovered but not dispatched.
> - //
> - Status = MmDispatcher ();
> -
> - //
> - // Check to see if CommBuffer and CommBufferSize are valid
> - //
> - if (CommBuffer != NULL && CommBufferSize != NULL) {
> - if (*CommBufferSize > 0) {
> - if (Status == EFI_NOT_READY) {
> - //
> - // If a the MM Core Entry Point was just registered, then set flag to
> - // request the MM Dispatcher to be restarted.
> - //
> - *(UINT8 *)CommBuffer = COMM_BUFFER_MM_DISPATCH_RESTART;
> - } else if (!EFI_ERROR (Status)) {
> - //
> - // Set the flag to show that the MM Dispatcher executed without errors
> - //
> - *(UINT8 *)CommBuffer = COMM_BUFFER_MM_DISPATCH_SUCCESS;
> - } else {
> - //
> - // Set the flag to show that the MM Dispatcher encountered an error
> - //
> - *(UINT8 *)CommBuffer = COMM_BUFFER_MM_DISPATCH_ERROR;
> - }
> - }
> - }
> -
> - return EFI_SUCCESS;
> -}
> -
> /**
> This function is the main entry point for an MM handler dispatch
> or communicate-based callback.
> diff --git a/StandaloneMmPkg/Core/StandaloneMmCore.c b/StandaloneMmPkg/Core/StandaloneMmCore.c
> index 74432320bfc7..ec53b8d8bec4 100644
> --- a/StandaloneMmPkg/Core/StandaloneMmCore.c
> +++ b/StandaloneMmPkg/Core/StandaloneMmCore.c
> @@ -100,7 +100,6 @@ BOOLEAN mInLegacyBoot = FALSE;
> //
> MM_CORE_MMI_HANDLERS mMmCoreMmiHandlers[] = {
> { MmFvDispatchHandler, &gMmFvDispatchGuid, NULL, TRUE },
> - { MmDriverDispatchHandler, &gEfiEventDxeDispatchGuid, NULL, TRUE },
> { MmReadyToLockHandler, &gEfiDxeMmReadyToLockProtocolGuid, NULL, TRUE },
> { MmEndOfDxeHandler, &gEfiEndOfDxeEventGroupGuid, NULL, FALSE },
> { MmLegacyBootHandler, &gEfiEventLegacyBootGuid, NULL, FALSE },
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-03-06 16:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 13:32 [PATCH 00/10] StandaloneMmPkg, ArmPkg: cleanups and improvements Ard Biesheuvel
2019-03-05 13:32 ` [PATCH 01/10] StandaloneMmPkg: drop redundant definition of gEfiMmConfigurationProtocolGuid Ard Biesheuvel
2019-03-05 13:53 ` Yao, Jiewen
2019-03-05 13:32 ` [PATCH 02/10] StandaloneMmPkg: drop unused PCD PcdStandaloneMmEnable Ard Biesheuvel
2019-03-05 13:55 ` Yao, Jiewen
2019-03-06 15:16 ` Achin Gupta
2019-03-06 15:17 ` Ard Biesheuvel
2019-03-06 15:37 ` Achin Gupta
2019-03-07 10:09 ` Ard Biesheuvel
2019-03-07 11:14 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 03/10] StandaloneMmPkg: switch to NULL DebugLib resolution Ard Biesheuvel
2019-03-05 14:22 ` Yao, Jiewen
2019-03-06 15:38 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 04/10] StandaloneMmPkg: remove redundant StandaloneMmDriverEntryPoint driver Ard Biesheuvel
2019-03-05 14:22 ` Yao, Jiewen
2019-03-05 13:32 ` [PATCH 05/10] StandaloneMmPkg/StandaloneMmCoreEntryPoint: drop explicit SerialPortLib call Ard Biesheuvel
2019-03-05 13:52 ` Yao, Jiewen
2019-03-06 16:35 ` Achin Gupta
2019-03-06 16:41 ` Ard Biesheuvel
2019-03-06 16:55 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 06/10] StandaloneMmPkg/Core: permit encapsulated firmware volumes Ard Biesheuvel
2019-03-05 15:50 ` Yao, Jiewen
2019-03-06 16:56 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 07/10] StandaloneMmPkg/Core: dispatch all drivers at init time Ard Biesheuvel
2019-03-05 15:51 ` Yao, Jiewen
2019-03-06 16:56 ` Achin Gupta [this message]
2019-03-05 13:32 ` [PATCH 08/10] StandaloneMmPkg/Core: drop support for dispatching FVs into MM Ard Biesheuvel
2019-03-05 15:51 ` Yao, Jiewen
2019-03-06 16:58 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 09/10] StandaloneMmPkg/Core: remove legacy boot support Ard Biesheuvel
2019-03-05 13:52 ` Yao, Jiewen
2019-03-06 16:59 ` Achin Gupta
2019-03-05 13:32 ` [PATCH 10/10] ArmPkg/MmCommunicationDxe: signal architected PI events into MM context Ard Biesheuvel
2019-03-05 15:55 ` Yao, Jiewen
2019-03-05 15:58 ` Ard Biesheuvel
2019-03-05 16:04 ` Yao, Jiewen
2019-03-05 16:07 ` Ard Biesheuvel
2019-03-05 16:19 ` Yao, Jiewen
2019-03-05 16:53 ` Felix Polyudov
2019-03-05 17:29 ` Ard Biesheuvel
2019-03-06 16:58 ` Achin Gupta
2019-03-11 11:54 ` [PATCH 00/10] StandaloneMmPkg, ArmPkg: cleanups and improvements Ard Biesheuvel
2019-03-11 11:59 ` Ard Biesheuvel
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=20190306165648.GT21602@mac-ubuntu-vm \
--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