public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel@lists.01.org
Subject: Re: [PATCH 2/2] ArmPlatformPkg/MemoryInitPeiLib: reserve rather than remove FV memory
Date: Wed, 28 Feb 2018 15:55:59 +0000	[thread overview]
Message-ID: <20180228155559.gbnaduc55omygecp@bivouac.eciton.net> (raw)
In-Reply-To: <20180228154441.10554-2-ard.biesheuvel@linaro.org>

On Wed, Feb 28, 2018 at 03:44:41PM +0000, Ard Biesheuvel wrote:
> Instead of completely removing the memory occupied by the primary PrePi
> FV from the memory map, thereby making it inaccessible to the OS, mark
> it as boot services data. This will ensure that the memory is left
> untouched by the firmware, but will release it to the OS when it calls
> ExitBootServices().
> 
> Note that for reasons that are not entirely clear, this only works as
> desired if the memory allocation HOB and the resource descriptor HOB
> that describe the region are identical in offset and size, and so we
> still need to iterate over the descriptors and split them up.
> 
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

Thanks for the rework - for the series:
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

> ---
>  ArmPlatformPkg/MemoryInitPei/MemoryInitPeiLib.c | 21 ++++++++++++--------
>  1 file changed, 13 insertions(+), 8 deletions(-)
> 
> diff --git a/ArmPlatformPkg/MemoryInitPei/MemoryInitPeiLib.c b/ArmPlatformPkg/MemoryInitPei/MemoryInitPeiLib.c
> index 2feb11f21d5d..01fd028dbd55 100644
> --- a/ArmPlatformPkg/MemoryInitPei/MemoryInitPeiLib.c
> +++ b/ArmPlatformPkg/MemoryInitPei/MemoryInitPeiLib.c
> @@ -129,7 +129,8 @@ MemoryPeim (
>    FdTop = (EFI_PHYSICAL_ADDRESS)PcdGet64 (PcdFdBaseAddress) + (EFI_PHYSICAL_ADDRESS)PcdGet32 (PcdFdSize);
>  
>    // EDK2 does not have the concept of boot firmware copied into DRAM. To avoid the DXE
> -  // core to overwrite this area we must mark the region with the attribute non-present
> +  // core to overwrite this area we must create a memory allocation HOB for the region,
> +  // but this only works if we split off the underlying resource descriptor as well.
>    if ((PcdGet64 (PcdFdBaseAddress) >= PcdGet64 (PcdSystemMemoryBase)) && (FdTop <= SystemMemoryTop)) {
>      Found = FALSE;
>  
> @@ -145,12 +146,10 @@ MemoryPeim (
>          ResourceTop = NextHob.ResourceDescriptor->PhysicalStart + ResourceLength;
>  
>          if (PcdGet64 (PcdFdBaseAddress) == NextHob.ResourceDescriptor->PhysicalStart) {
> -          if (SystemMemoryTop == FdTop) {
> -            NextHob.ResourceDescriptor->ResourceAttribute = ResourceAttributes & ~EFI_RESOURCE_ATTRIBUTE_PRESENT;
> -          } else {
> -            // Create the System Memory HOB for the firmware with the non-present attribute
> +          if (SystemMemoryTop != FdTop) {
> +            // Create the System Memory HOB for the firmware
>              BuildResourceDescriptorHob (EFI_RESOURCE_SYSTEM_MEMORY,
> -                                        ResourceAttributes & ~EFI_RESOURCE_ATTRIBUTE_PRESENT,
> +                                        ResourceAttributes,
>                                          PcdGet64 (PcdFdBaseAddress),
>                                          PcdGet32 (PcdFdSize));
>  
> @@ -159,9 +158,9 @@ MemoryPeim (
>              NextHob.ResourceDescriptor->ResourceLength -= PcdGet32(PcdFdSize);
>            }
>          } else {
> -          // Create the System Memory HOB for the firmware with the non-present attribute
> +          // Create the System Memory HOB for the firmware
>            BuildResourceDescriptorHob (EFI_RESOURCE_SYSTEM_MEMORY,
> -                                      ResourceAttributes & ~EFI_RESOURCE_ATTRIBUTE_PRESENT,
> +                                      ResourceAttributes,
>                                        PcdGet64 (PcdFdBaseAddress),
>                                        PcdGet32 (PcdFdSize));
>  
> @@ -177,6 +176,12 @@ MemoryPeim (
>                                          ResourceTop - FdTop);
>            }
>          }
> +
> +        // Mark the memory covering the Firmware Device as boot services data
> +        BuildMemoryAllocationHob (PcdGet64 (PcdFdBaseAddress),
> +                                  PcdGet32 (PcdFdSize),
> +                                  EfiBootServicesData);
> +
>          Found = TRUE;
>          break;
>        }
> -- 
> 2.11.0
> 


  reply	other threads:[~2018-02-28 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 15:44 [PATCH 1/2] ArmPlatformPkg/MemoryInitPeiLib: revert "don't reserve primary FV in memory" Ard Biesheuvel
2018-02-28 15:44 ` [PATCH 2/2] ArmPlatformPkg/MemoryInitPeiLib: reserve rather than remove FV memory Ard Biesheuvel
2018-02-28 15:55   ` Leif Lindholm [this message]
2018-02-28 16:12     ` 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=20180228155559.gbnaduc55omygecp@bivouac.eciton.net \
    --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