This routine triggers a reset after every time mytstapp.efi runs, when any UEFI
Boot Manager boot option is subsequently selected (EFI Shell, OS loader,
mytstapp.efi, etc.)
I drove myself crazy for a while making sure that mytstapp.efi doesn't leak,
and now I sleep a little better at night knowing it doesn't. :)
So apparently this routine will reset the system based on the memory usage
stats.
This seems horribly broken!
a) It's never a good experience when you are at the UEFI Boot Menu, and
you select to run something, and the system resets, d'oh!
b) Why is mytstapp.efi dictating the memory type information (reserved?)
for the system?
I don't understand the reservation adjustment. The memory map looks largely
the same after the reset.
Is there some way mytstapp.efi can opt out of the usage stats, since it has
such bizarre effects on the memory type information?
//
// Retrieve the current memory usage statistics. If they are not found, then
// no adjustments can be made to the Memory Type Information variable.
//
Status = EfiGetSystemConfigurationTable (
&gEfiMemoryTypeInformationGuid,
(VOID **) &CurrentMemoryTypeInformation
);
Thanks!
__e
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
