From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=17.171.2.34; helo=mail-in24.apple.com; envelope-from=afish@apple.com; receiver=edk2-devel@lists.01.org Received: from mail-in24.apple.com (mail-out24.apple.com [17.171.2.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 00241210C642A for ; Thu, 2 Aug 2018 07:37:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1533220663; x=2397134263; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=owJUszjWlHuGSpZvUd2jJGN/hl86CVz9bWqMzd/PT+c=; b=tPuvhEFzl3HfGs4y7yzwJLpwvYI0Itmi2rJ2fyCIAtfAx5tySOmC5NbUDsWanBiU AhgvZTk2j23SDEAJae2agWARB0S/zI8FRptYs7Y59MpK0TI86v86z480Ml0ELe3y CUF9QmGHdiufqEy/6lC9cstMjXSchs9eY2vOuMF4F2HibcFyehuW0m3nPAQHc8Fn I2wkt1IpQnhGUpR1eWGXYjGKw89+SuZxnB0sliN6ihPCmpzICqWG000kfnOYUv26 7b0dPl3a9fpRG3W5Cn7UcsTH8fwWBQa2t0QxiturLLkdEEQQurMPfNKlJbb66bQK bC9Kx0QqfbnCpMbIyLPWwg==; X-AuditID: 11ab0218-0d1ff70000001a2c-68-5b6317377b49 Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail-in24.apple.com (Apple Secure Mail Relay) with SMTP id 32.CA.06700.737136B5; Thu, 2 Aug 2018 07:37:43 -0700 (PDT) MIME-version: 1.0 Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PCU007R28MVT070@ma1-mtap-s01.corp.apple.com>; Thu, 02 Aug 2018 07:37:43 -0700 (PDT) Received: from process_viserion-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PCU00K0084NBY00@nwk-mmpp-sz12.apple.com>; Thu, 02 Aug 2018 07:37:43 -0700 (PDT) X-Va-A: X-Va-T-CD: 7b94995cc9f7b636481b394f88e9b0f7 X-Va-E-CD: 3960c102e12701346900df67a23f3972 X-Va-R-CD: d1ffea336cad1ce020d2c7bb490c171e X-Va-CD: 0 X-Va-ID: 7d7f8f00-ba2a-47bc-bbdd-cfa1f1d75c58 X-V-A: X-V-T-CD: 7b94995cc9f7b636481b394f88e9b0f7 X-V-E-CD: 3960c102e12701346900df67a23f3972 X-V-R-CD: d1ffea336cad1ce020d2c7bb490c171e X-V-CD: 0 X-V-ID: 156dff9c-d874-4ba3-a3c7-829d0d1db77c Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PCU00K0083UBP00@nwk-mmpp-sz12.apple.com>; Thu, 02 Aug 2018 07:37:42 -0700 (PDT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-02_03:,, signatures=0 X-Proofpoint-Scanner-Instance: nwk-grpmailp-qapp15.corp.apple.com-10000_instance1 Received: from [17.234.110.24] (unknown [17.234.110.24]) by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PCU00A078MTGI10@nwk-mmpp-sz12.apple.com>; Thu, 02 Aug 2018 07:37:42 -0700 (PDT) Sender: afish@apple.com From: Andrew Fish Message-id: <694BC161-9845-48D4-BBDF-8D7E1A77B285@apple.com> Date: Thu, 02 Aug 2018 07:37:40 -0700 In-reply-to: Cc: "Ni, Ruiyu" , "edk2-devel@lists.01.org" , "Yao, Jiewen" To: Rafael Machado References: <74D8A39837DF1E4DA445A8C0B3885C503AC75235@shsmsx102.ccr.corp.intel.com> <734D49CCEBEEF84792F5B80ED585239D5BD4FFA1@SHSMSX104.ccr.corp.intel.com> <17C6FC15-6D2E-41A6-8996-15E665C4D28F@apple.com> X-Mailer: Apple Mail (2.3445.6.18) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnleLIzCtJLcpLzFFi42IR1PBh1TUXT442WL/JxGLPoaPMFus+eljs fDmD3eJlz2p2BxaPnbPusnss3vOSyaN79j+WAOYoLpuU1JzMstQifbsErowtt5azFfRdYqn4 +vsjYwPj4haWLkZODgkBE4mbX1YxdjFycQgJ7GeSmP5gHSNIgldAUOLH5HtgRcwCYRIfHi5n gijayCSxYfsSKKeLSeLvhx/sEKPYJf782gE1Vluia/t8Rhj76r//cPFzh9qh6rkkFmw9zQph 60pMvnQJqoZNYv0JkAUgtpbEig1H4Oylr7azwNh7up5A2ZwS579MhJqpI3Fg9T1miOM6mSR+ L9oBlOAASmRLvNqgBlETLPHnUA9UzUQmiU3PGplBEsIC4hLvzmwCs9kElCVWzP/ADgkKG4nf XdeYIGpMJR52nwerYRFQlbj/cjpYnBNo6OLpD8GhwizQzCjR+G8v2HUiAmYSe2dNYIfYtpxZ Ys3Pw1CnKkn833WEeQKjwiyk8J6FFN6zgA5nFlCXmDIlFyKsLfHk3QVWCFtNYuHvRUzI4gsY 2VYxCucmZuboZuYZmeglFhTkpOol5+duYgSloNVMEjsYv7w2PMQowMGoxMN7gyEpWog1say4 MvcQozQHi5I478ddYtFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGLnKVxUGHLr/aeHVAIbl rX7xS1+aemoavmRMN5jiGHs/8advx4/yk7faEirn2ZSGOgQzX6w1Sp1cb/x/Zo8ex+N/i5y/ XApx/CtsvkdCVvGNcYb/jP1vZn4J/nJo2ydJrWj7oyuj/jm4qrgdP6ZUtqTD4NOqrux1X94a JSt1CXjfCz2+tsV4rxJLcUaioRZzUXEiALnypEYiAwAA X-Content-Filtered-By: Mailman/MimeDel 2.1.27 Subject: Re: Question about memory map entries X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 14:37:45 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Aug 2, 2018, at 5:39 AM, Rafael Machado = wrote: >=20 > Hi everyone >=20 > After some other tasks I am back to this case :) >=20 > After some debug, we detected the moment where things start to go = wrong, but I am not sure what may cause this. >=20 > What we noticed is that the following assert is reached: > = https://github.com/tianocore/edk2/blob/87acb6e298e718250dd8b741b6888a3a54c= 7cb5a/MdeModulePkg/Core/Dxe/Gcd/Gcd.c#L21 = h = 99 = > Just to remember, this assert is reached with the following steps: > 1 - Boot the application (renamed to BOOTX64.efi) from a usb stick > 2 - Execute the application tasks > 3 - exit the application (free everything, all events closed and no = memory leaks detected as suggested to check by Andrew on the previous = e-mail, then return efi_success) > 4 - the system will reboot and reach the assert >=20 > But it does not happen with the following scenario: > 1 - Boot the application (renamed to BOOTX64.efi) from a usb stick > 2 - Execute the application tasks > 3 - Power off the system >=20 > As far as I could understand (please correct my understanding that may = be wrong since is the first time I look at this part of the code), at = this point the HOBs passed from sec phase are processed by PEI so the = memory could be "detected/mapped/initialized" correctly. But for some = reason the required HOB is no present at the list. >=20 > Could someone with more experience at this part of the code please = confirm my understanding, and if possible give some guesses about what = could cause this scenario? >=20 > My guess is that some memory cleanup that should be done by the bios = after the application exits is not being done correctly. So I believe = the problem is not at the application, but at the BIOS. A friend here = mentioned about the MemoryTypeInformation efi var, that may be = corrupted, and considering it's used to guide the boot process it may = impact the boot, but I am not sure if this is the case and also I didn't = find to much information about this var and it's usage, so any help = about this would be well received also. >=20 > Any ideas? >=20 Rafael, The gEfiMemoryTypeInformationGuid HOB is optional and used to defragment = the EFI Memory Map. While it is copied it is not really in use at the = point of your ASSERT.=20 The PHIT HOB[1] must be the 1st HOB entry and it is the layout of the = memory that was in use by the PEI phase. At this point int he boot it is = likely the memory registered in PEI via the InstallPeiMemory() PEI = Service. The error is the memory in the PHIT hob does not have a = corresponding EFI_HOB_TYPE_RESOURCE_DESCRIPTOR of type = EFI_RESOURCE_SYSTEM_MEMORY. Here is an example of code doing the registration. As you can see it = calls PeiServicesInstallPeiMemory() and also generates the Resource HOB.=20= = https://github.com/tianocore/edk2/blob/master/QuarkPlatformPkg/Platform/Pe= i/PlatformInit/MrcWrapper.c#L738 You could try to track down the code in your code base doing the above = operation, and if that looks OK maybe add DEBUG prints and dump out the = HOBs to see if the got corrupted some how? [1] PHIT HOB /// /// Contains general state information used by the HOB producer phase. /// This HOB must be the first one in the HOB list. /// typedef struct { /// /// The HOB generic header. Header.HobType =3D EFI_HOB_TYPE_HANDOFF. /// EFI_HOB_GENERIC_HEADER Header; /// /// The version number pertaining to the PHIT HOB definition. /// This value is four bytes in length to provide an 8-byte aligned = entry /// when it is combined with the 4-byte BootMode. /// UINT32 Version; /// /// The system boot mode as determined during the HOB producer phase. /// EFI_BOOT_MODE BootMode; /// /// The highest address location of memory that is allocated for use = by the HOB producer /// phase. This address must be 4-KB aligned to meet page restrictions = of UEFI. /// EFI_PHYSICAL_ADDRESS EfiMemoryTop; /// /// The lowest address location of memory that is allocated for use by = the HOB producer phase. /// EFI_PHYSICAL_ADDRESS EfiMemoryBottom; /// /// The highest address location of free memory that is currently = available /// for use by the HOB producer phase. /// EFI_PHYSICAL_ADDRESS EfiFreeMemoryTop; /// /// The lowest address location of free memory that is available for = use by the HOB producer phase. /// EFI_PHYSICAL_ADDRESS EfiFreeMemoryBottom; /// /// The end of the HOB list. /// EFI_PHYSICAL_ADDRESS EfiEndOfHobList; } EFI_HOB_HANDOFF_INFO_TABLE; Thanks, Andrew Fish > Thanks and Regards > Rafael R. Machado >=20 > Em s=C3=A1b, 30 de jun de 2018 =C3=A0s 16:23, Andrew Fish = > escreveu: >=20 >=20 > > On Jun 30, 2018, at 5:02 AM, Rafael Machado = > wrote: > >=20 > > Hi everyone. Thanks for the answers! > > In this case, I just executed 3 shell command: > >=20 > > memmap >> before.txt > > app.efi > > memmap >> after.txt > >=20 > > Does anyone could clarify what could cause a new entry to be created = at the > > memmap output command? >=20 > There is fragmentation caused the Apps high usage of memory and this = can cause a lot more entries. I guess the DXE Core might also need to = allocate some extra pages to track the fragmentation of the memory pool = caused by the App.=20 >=20 > > My understanding was that the entries at the memmap command reflect = the GCD > > (global coherence domain), that is something that should not change = too > > much after the system is already at BDS phase. >=20 > It is not really showing you GCD, it is showing the UEFI memory map. = GCD implies the memory is being used as DRAM by the CPU , the UEFI = memory map tracks the type of allocation and what areas of memory are = free. That usage patter is changed by your App running.=20 >=20 > > As mentioned, the > > application does a lot of AllocatePool() FreePool() calls. And these = calls > > are, as far as I could understand, creating a lot of entries of type = "BS_Data" > > and "Available". > > Shouldn't the bios allocation routines try to reuse the pools = already used > > and freed to avoid massing and fragmenting the memory? > >=20 > > Besides that, we just found a system that hangs on the subsequent = boot > > after executing the application. The strange is that the system just = hangs > > if you do the following steps: > >=20 > > 1 - execute the application: app.efi > > 2 - exit the shell with the command: exit > > 3 - boot hangs not presenting the shell prompt > >=20 > >=20 > > In case you do the following steps the hang doesn't happen: > >=20 > > 1 - execute the application: app.efi > > 2 - shut down the system by pressing the power button > > 3 - boots normally entering at the shell prompt > >=20 > > Any idea about what could cause this strange behavior, and if this = may have > > some relation with the increase of the memmap output entries? >=20 > A common bug is for an Application to not clean up something and have = the resource get freed. For example the App starts a timer event, = forgets to stop it and when the App exits the memory gets freed back and = if some one else allocates that memory they overwrite the code that = executes in the timer event and kaboom. Same goes for publishing a = protocol, etc.=20 >=20 > Given the issue is only with your App I'd focus on the App and not the = delta in the memory map.=20 >=20 > On thing that may be helpful is to turn on this property it will cause = the freed pool to get filled with 0xAF. 0xAFAFAFAFAFAFAFAF will GP fault = if it is used as a memory address so this helps catch using freed = resources closer to the source.=20 > PcdDebugPropertyMask set DEBUG_PROPERTY_CLEAR_MEMORY_ENABLED >=20 > Thanks, >=20 > Andrew Fish >=20 > > (maybe > > something related with the MemoryTypeInformation information that = seems to > > be saved to make the subsequent boots easier from the bios = perspective. > > This guess is based on [1] page 19, that explains the creation of = the > > BIN.DXE, but things are a little dark to me yet. Not sure if my > > understanding is correct.) > >=20 > > [1] > > = https://firmware.intel.com/sites/default/files/resources/A_Tour_Beyond_BIO= S_Memory_Map_in%20UEFI_BIOS.pdf = > >=20 > > Thanks and Regards > > Rafael R. Machado > >=20 > > Em sex, 29 de jun de 2018 =C3=A0s 22:31, Ni, Ruiyu = > escreveu: > >=20 > >> Yes. > >> Check the PCD PcdShellMaxHistoryCommandCount (0x20) which sets > >> the maximum command history. > >> The memmap output should be stable after you run more than > >> 0x20 commands. > >>=20 > >>> -----Original Message----- > >>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org = ] On Behalf Of > >> Yao, > >>> Jiewen > >>> Sent: Saturday, June 30, 2018 3:28 AM > >>> To: Rafael Machado >; edk2- > >>> devel@lists.01.org > >>> Subject: Re: [edk2] Question about memory map entries > >>>=20 > >>> Shell itself may allocate internal buffer to save something, such = as > >> history. > >>>=20 > >>> Thank you > >>> Yao Jiewen > >>>=20 > >>>> -----Original Message----- > >>>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org = ] On Behalf Of > >>>> Rafael Machado > >>>> Sent: Friday, June 29, 2018 12:06 PM > >>>> To: edk2-devel@lists.01.org > >>>> Subject: [edk2] Question about memory map entries > >>>>=20 > >>>> Hi everyone > >>>>=20 > >>>> I have a question related to the memory map entries. > >>>> Doing some tests, we noticed that if I have an application that = has a > >>>> lot of allocatepool() and freepool() calls, when this app is = closed > >>>> the amount of entries returned by the memmap shell commands = increases a > >>> lot. > >>>>=20 > >>>> Just for reference. This is the mapping before executing the > >> application: > >>>>=20 > >>>> Type Start End # Pages > >>>> Attributes > >>>> BS_Code 0000000000000000-0000000000000FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Data 0000000000001000-0000000000001FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Code 0000000000002000-000000000000BFFF 000000000000000A > >>>> 000000000000000F > >>>> Available 000000000000C000-0000000000057FFF 000000000000004C > >>>> 000000000000000F > >>>> Reserved 0000000000058000-0000000000058FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000000059000-0000000000069FFF 0000000000000011 > >>>> 000000000000000F > >>>> BS_Data 000000000006A000-000000000006AFFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Code 000000000006B000-000000000008BFFF 0000000000000021 > >>>> 000000000000000F > >>>> Reserved 000000000008C000-000000000009FFFF 0000000000000014 > >>>> 000000000000000F > >>>> BS_Code 0000000000100000-000000000010FFFF 0000000000000010 > >>>> 000000000000000F > >>>> Available 0000000000110000-000000004D684FFF 000000000004D575 > >>>> 000000000000000F > >>>> BS_Data 000000004D685000-000000004D6A4FFF 0000000000000020 > >>>> 000000000000000F > >>>> Available 000000004D6A5000-000000004E34EFFF 0000000000000CAA > >>>> 000000000000000F LoaderCode 000000004E34F000-000000004E42CFFF > >>>> 00000000000000DE 000000000000000F > >>>> BS_Data 000000004E42D000-0000000050510FFF 00000000000020E4 > >>>> 000000000000000F > >>>> ACPI_NVS 0000000050511000-0000000050511FFF 0000000000000001 > >>>> 000000000000000F > >>>> RT_Data 0000000050512000-0000000050512FFF 0000000000000001 > >>>> 800000000000000F > >>>> BS_Data 0000000050513000-0000000050673FFF 0000000000000161 > >>>> 000000000000000F > >>>> BS_Code 0000000050674000-0000000050674FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000050675000-0000000052B6EFFF 00000000000024FA > >>>> 000000000000000F > >>>> BS_Data 0000000052B6F000-0000000053572FFF 0000000000000A04 > >>>> 000000000000000F > >>>> Available 0000000053573000-0000000053834FFF 00000000000002C2 > >>>> 000000000000000F > >>>> BS_Data 0000000053835000-0000000053A0DFFF 00000000000001D9 > >>>> 000000000000000F > >>>> Available 0000000053A0E000-0000000053A64FFF 0000000000000057 > >>>> 000000000000000F > >>>> BS_Data 0000000053A65000-0000000054778FFF 0000000000000D14 > >>>> 000000000000000F > >>>> Available 0000000054779000-0000000054785FFF 000000000000000D > >>>> 000000000000000F > >>>> BS_Data 0000000054786000-00000000547CAFFF 0000000000000045 > >>>> 000000000000000F > >>>> Available 00000000547CB000-00000000547D3FFF 0000000000000009 > >>>> 000000000000000F > >>>> BS_Data 00000000547D4000-000000005481DFFF 000000000000004A > >>>> 000000000000000F > >>>> Available 000000005481E000-000000005481FFFF 0000000000000002 > >>>> 000000000000000F > >>>> BS_Data 0000000054820000-0000000056683FFF 0000000000001E64 > >>>> 000000000000000F > >>>> Available 0000000056684000-00000000590C2FFF 0000000000002A3F > >>>> 000000000000000F > >>>> BS_Code 00000000590C3000-0000000059E83FFF 0000000000000DC1 > >>>> 000000000000000F > >>>> RT_Code 0000000059E84000-0000000059F4BFFF 00000000000000C8 > >>>> 800000000000000F > >>>> RT_Data 0000000059F4C000-000000005B164FFF 0000000000001219 > >>>> 800000000000000F > >>>> Reserved 000000005B165000-000000005B566FFF 0000000000000402 > >>>> 000000000000000F > >>>> ACPI_NVS 000000005B567000-000000005B599FFF 0000000000000033 > >>>> 000000000000000F > >>>> ACPI_Recl 000000005B59A000-000000005B5FEFFF 0000000000000065 > >>>> 000000000000000F > >>>> BS_Data 000000005B5FF000-000000005B5FFFFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000100000000-000000029E7FFFFF 000000000019E800 > >>>> 000000000000000F > >>>> Reserved 00000000000A0000-00000000000FFFFF 0000000000000060 > >>>> 0000000000000000 > >>>> Reserved 000000005B600000-000000005F7FFFFF 0000000000004200 > >>>> 0000000000000000 > >>>> MMIO 00000000F0000000-00000000F7FFFFFF 0000000000008000 > >>>> 8000000000000001 > >>>> MMIO 00000000FE010000-00000000FE010FFF 0000000000000001 > >>>> 8000000000000001 > >>>>=20 > >>>> Reserved : 18,039 Pages (73,887,744 Bytes) > >>>> LoaderCode: 222 Pages (909,312 Bytes) > >>>> LoaderData: 0 Pages (0 Bytes) > >>>> BS_Code : 3,582 Pages (14,671,872 Bytes) > >>>> BS_Data : 23,116 Pages (94,683,136 Bytes) > >>>> RT_Code : 200 Pages (819,200 Bytes) > >>>> RT_Data : 4,634 Pages (18,980,864 Bytes) > >>>> ACPI_Recl : 101 Pages (413,696 Bytes) > >>>> ACPI_NVS : 52 Pages (212,992 Bytes) > >>>> MMIO : 32,769 Pages (134,221,824 Bytes) > >>>> MMIO_Port : 0 Pages (0 Bytes) > >>>> PalCode : 0 Pages (0 Bytes) > >>>> Available : 2,039,014 Pages (8,351,801,344 Bytes) > >>>> -------------- > >>>> Total Memory: 8,089 MB (8,482,492,416 Bytes) > >>>>=20 > >>>>=20 > >>>>=20 > >>>> And this is the mapping after executing the application. > >>>>=20 > >>>>=20 > >>>> Type Start End # Pages > >>>> Attributes > >>>> BS_Code 0000000000000000-0000000000000FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Data 0000000000001000-0000000000001FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Code 0000000000002000-000000000000BFFF 000000000000000A > >>>> 000000000000000F > >>>> Available 000000000000C000-0000000000057FFF 000000000000004C > >>>> 000000000000000F > >>>> Reserved 0000000000058000-0000000000058FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000000059000-0000000000069FFF 0000000000000011 > >>>> 000000000000000F > >>>> BS_Data 000000000006A000-000000000006AFFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Code 000000000006B000-000000000008BFFF 0000000000000021 > >>>> 000000000000000F > >>>> Reserved 000000000008C000-000000000009FFFF 0000000000000014 > >>>> 000000000000000F > >>>> BS_Code 0000000000100000-000000000010FFFF 0000000000000010 > >>>> 000000000000000F > >>>> Available 0000000000110000-000000004D684FFF 000000000004D575 > >>>> 000000000000000F > >>>> BS_Data 000000004D685000-000000004D6A4FFF 0000000000000020 > >>>> 000000000000000F > >>>> Available 000000004D6A5000-000000004E34EFFF 0000000000000CAA > >>>> 000000000000000F LoaderCode 000000004E34F000-000000004E42CFFF > >>>> 00000000000000DE 000000000000000F > >>>> BS_Data 000000004E42D000-0000000050510FFF 00000000000020E4 > >>>> 000000000000000F > >>>> ACPI_NVS 0000000050511000-0000000050511FFF 0000000000000001 > >>>> 000000000000000F > >>>> RT_Data 0000000050512000-0000000050512FFF 0000000000000001 > >>>> 800000000000000F > >>>> BS_Data 0000000050513000-0000000050673FFF 0000000000000161 > >>>> 000000000000000F > >>>> BS_Code 0000000050674000-0000000050674FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000050675000-0000000052384FFF 0000000000001D10 > >>>> 000000000000000F > >>>> BS_Data 0000000052385000-0000000053572FFF 00000000000011EE > >>>> 000000000000000F > >>>> Available 0000000053573000-00000000535D7FFF 0000000000000065 > >>>> 000000000000000F > >>>> BS_Data 00000000535D8000-000000005363EFFF 0000000000000067 > >>>> 000000000000000F > >>>> Available 000000005363F000-0000000053834FFF 00000000000001F6 > >>>> 000000000000000F > >>>> BS_Data 0000000053835000-0000000053A0DFFF 00000000000001D9 > >>>> 000000000000000F > >>>> Available 0000000053A0E000-0000000053A64FFF 0000000000000057 > >>>> 000000000000000F > >>>> BS_Data 0000000053A65000-0000000053F8EFFF 000000000000052A > >>>> 000000000000000F > >>>> Available 0000000053F8F000-0000000053F9AFFF 000000000000000C > >>>> 000000000000000F > >>>> BS_Data 0000000053F9B000-0000000053F9CFFF 0000000000000002 > >>>> 000000000000000F > >>>> Available 0000000053F9D000-0000000053FA5FFF 0000000000000009 > >>>> 000000000000000F > >>>> BS_Data 0000000053FA6000-0000000053FAAFFF 0000000000000005 > >>>> 000000000000000F > >>>> Available 0000000053FAB000-000000005438CFFF 00000000000003E2 > >>>> 000000000000000F > >>>> BS_Data 000000005438D000-00000000543A5FFF 0000000000000019 > >>>> 000000000000000F > >>>> Available 00000000543A6000-0000000054416FFF 0000000000000071 > >>>> 000000000000000F > >>>> BS_Data 0000000054417000-0000000054417FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000054418000-0000000054425FFF 000000000000000E > >>>> 000000000000000F > >>>> BS_Data 0000000054426000-0000000054427FFF 0000000000000002 > >>>> 000000000000000F > >>>> Available 0000000054428000-0000000054439FFF 0000000000000012 > >>>> 000000000000000F > >>>> BS_Data 000000005443A000-000000005443FFFF 0000000000000006 > >>>> 000000000000000F > >>>> Available 0000000054440000-000000005444FFFF 0000000000000010 > >>>> 000000000000000F > >>>> BS_Data 0000000054450000-0000000054454FFF 0000000000000005 > >>>> 000000000000000F > >>>> Available 0000000054455000-0000000054458FFF 0000000000000004 > >>>> 000000000000000F > >>>> BS_Data 0000000054459000-000000005445BFFF 0000000000000003 > >>>> 000000000000000F > >>>> Available 000000005445C000-0000000054467FFF 000000000000000C > >>>> 000000000000000F > >>>> BS_Data 0000000054468000-000000005446BFFF 0000000000000004 > >>>> 000000000000000F > >>>> Available 000000005446C000-000000005446FFFF 0000000000000004 > >>>> 000000000000000F > >>>> BS_Data 0000000054470000-0000000054470FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000054471000-0000000054471FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Data 0000000054472000-0000000054474FFF 0000000000000003 > >>>> 000000000000000F > >>>> Available 0000000054475000-0000000054490FFF 000000000000001C > >>>> 000000000000000F > >>>> BS_Data 0000000054491000-0000000054494FFF 0000000000000004 > >>>> 000000000000000F > >>>> Available 0000000054495000-00000000544ABFFF 0000000000000017 > >>>> 000000000000000F > >>>> BS_Data 00000000544AC000-00000000544ACFFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 00000000544AD000-00000000544CCFFF 0000000000000020 > >>>> 000000000000000F > >>>> BS_Data 00000000544CD000-00000000544CFFFF 0000000000000003 > >>>> 000000000000000F > >>>> Available 00000000544D0000-00000000544E1FFF 0000000000000012 > >>>> 000000000000000F > >>>> BS_Data 00000000544E2000-000000005450CFFF 000000000000002B > >>>> 000000000000000F > >>>> Available 000000005450D000-000000005451DFFF 0000000000000011 > >>>> 000000000000000F > >>>> BS_Data 000000005451E000-000000005451EFFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 000000005451F000-0000000054535FFF 0000000000000017 > >>>> 000000000000000F > >>>> BS_Data 0000000054536000-0000000054536FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000054537000-000000005453EFFF 0000000000000008 > >>>> 000000000000000F > >>>> BS_Data 000000005453F000-0000000054543FFF 0000000000000005 > >>>> 000000000000000F > >>>> Available 0000000054544000-0000000054579FFF 0000000000000036 > >>>> 000000000000000F > >>>> BS_Data 000000005457A000-0000000054585FFF 000000000000000C > >>>> 000000000000000F > >>>> Available 0000000054586000-0000000054589FFF 0000000000000004 > >>>> 000000000000000F > >>>> BS_Data 000000005458A000-000000005458CFFF 0000000000000003 > >>>> 000000000000000F > >>>> Available 000000005458D000-000000005459DFFF 0000000000000011 > >>>> 000000000000000F > >>>> BS_Data 000000005459E000-000000005459EFFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 000000005459F000-00000000545A1FFF 0000000000000003 > >>>> 000000000000000F > >>>> BS_Data 00000000545A2000-00000000545A2FFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 00000000545A3000-00000000545A7FFF 0000000000000005 > >>>> 000000000000000F > >>>> BS_Data 00000000545A8000-00000000545A9FFF 0000000000000002 > >>>> 000000000000000F > >>>> Available 00000000545AA000-0000000054756FFF 00000000000001AD > >>>> 000000000000000F > >>>> BS_Data 0000000054757000-000000005477EFFF 0000000000000028 > >>>> 000000000000000F > >>>> Available 000000005477F000-0000000054780FFF 0000000000000002 > >>>> 000000000000000F > >>>> BS_Data 0000000054781000-0000000054785FFF 0000000000000005 > >>>> 000000000000000F > >>>> Available 0000000054786000-0000000054789FFF 0000000000000004 > >>>> 000000000000000F > >>>> BS_Data 000000005478A000-00000000547CBFFF 0000000000000042 > >>>> 000000000000000F > >>>> Available 00000000547CC000-00000000547CEFFF 0000000000000003 > >>>> 000000000000000F > >>>> BS_Data 00000000547CF000-00000000547D3FFF 0000000000000005 > >>>> 000000000000000F > >>>> Available 00000000547D4000-00000000547E7FFF 0000000000000014 > >>>> 000000000000000F > >>>> BS_Data 00000000547E8000-00000000547F4FFF 000000000000000D > >>>> 000000000000000F > >>>> Available 00000000547F5000-00000000547FBFFF 0000000000000007 > >>>> 000000000000000F > >>>> BS_Data 00000000547FC000-000000005481EFFF 0000000000000023 > >>>> 000000000000000F > >>>> Available 000000005481F000-000000005481FFFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Data 0000000054820000-0000000054828FFF 0000000000000009 > >>>> 000000000000000F > >>>> Available 0000000054829000-0000000054829FFF 0000000000000001 > >>>> 000000000000000F > >>>> BS_Data 000000005482A000-0000000054CFAFFF 00000000000004D1 > >>>> 000000000000000F > >>>> Available 0000000054CFB000-0000000054CFCFFF 0000000000000002 > >>>> 000000000000000F > >>>> BS_Data 0000000054CFD000-0000000055269FFF 000000000000056D > >>>> 000000000000000F > >>>> Available 000000005526A000-000000005526EFFF 0000000000000005 > >>>> 000000000000000F > >>>> BS_Data 000000005526F000-0000000056683FFF 0000000000001415 > >>>> 000000000000000F > >>>> Available 0000000056684000-00000000590C2FFF 0000000000002A3F > >>>> 000000000000000F > >>>> BS_Code 00000000590C3000-0000000059E83FFF 0000000000000DC1 > >>>> 000000000000000F > >>>> RT_Code 0000000059E84000-0000000059F4BFFF 00000000000000C8 > >>>> 800000000000000F > >>>> RT_Data 0000000059F4C000-000000005B164FFF 0000000000001219 > >>>> 800000000000000F > >>>> Reserved 000000005B165000-000000005B566FFF 0000000000000402 > >>>> 000000000000000F > >>>> ACPI_NVS 000000005B567000-000000005B599FFF 0000000000000033 > >>>> 000000000000000F > >>>> ACPI_Recl 000000005B59A000-000000005B5FEFFF 0000000000000065 > >>>> 000000000000000F > >>>> BS_Data 000000005B5FF000-000000005B5FFFFF 0000000000000001 > >>>> 000000000000000F > >>>> Available 0000000100000000-000000029E7FFFFF 000000000019E800 > >>>> 000000000000000F > >>>> Reserved 00000000000A0000-00000000000FFFFF 0000000000000060 > >>>> 0000000000000000 > >>>> Reserved 000000005B600000-000000005F7FFFFF 0000000000004200 > >>>> 0000000000000000 > >>>> MMIO 00000000F0000000-00000000F7FFFFFF 0000000000008000 > >>>> 8000000000000001 > >>>> MMIO 00000000FE010000-00000000FE010FFF 0000000000000001 > >>>> 8000000000000001 > >>>>=20 > >>>> Reserved : 18,039 Pages (73,887,744 Bytes) > >>>> LoaderCode: 222 Pages (909,312 Bytes) > >>>> LoaderData: 0 Pages (0 Bytes) > >>>> BS_Code : 3,582 Pages (14,671,872 Bytes) > >>>> BS_Data : 23,366 Pages (95,707,136 Bytes) > >>>> RT_Code : 200 Pages (819,200 Bytes) > >>>> RT_Data : 4,634 Pages (18,980,864 Bytes) > >>>> ACPI_Recl : 101 Pages (413,696 Bytes) > >>>> ACPI_NVS : 52 Pages (212,992 Bytes) > >>>> MMIO : 32,769 Pages (134,221,824 Bytes) > >>>> MMIO_Port : 0 Pages (0 Bytes) > >>>> PalCode : 0 Pages (0 Bytes) > >>>> Available : 2,038,764 Pages (8,350,777,344 Bytes) > >>>> -------------- > >>>> Total Memory: 8,089 MB (8,482,492,416 Bytes) > >>>>=20 > >>>>=20 > >>>> I would like to understand better what causes these entries to be > >> created. > >>>> We already checked and there is no memory leak at the code. > >>>> What causes these entries to be created? > >>>> Can this increase on the memory map entries represent a risk of > >>>> hanging the system at the subsequent boot? > >>>>=20 > >>>> Thanks and Regards > >>>> Rafael R. Machado > >>>> _______________________________________________ > >>>> edk2-devel mailing list > >>>> edk2-devel@lists.01.org > >>>> https://lists.01.org/mailman/listinfo/edk2-devel = > >>> _______________________________________________ > >>> edk2-devel mailing list > >>> edk2-devel@lists.01.org > >>> https://lists.01.org/mailman/listinfo/edk2-devel = > >>=20 > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel = >=20