hi, Oliver:
I have a problem about stack setup for an ARM platform.
Based on an ArmRealViewEb-RTSM-A9x2.dsc.
During the boot procedure, there are 3 places to setup stacks:
1. _ModuleEntryPoint
Used these pcds to setup stack:
gArmPlatformTokenSpaceGuid.PcdCPUCoresSecStackBase|0x4B000000
2. enter_monitor_mode()
Used these pcds to setup stack:
gArmPlatformTokenSpaceGuid.PcdCPUCoresSecMonStackBase|0x4A000000
3. ArmPlatformPkg\PrePeiCore
Used these pcds to setup stack:
gArmPlatformTokenSpaceGuid.PcdCPUCoresStackBase|0x48000000
So, my question is:
1. Setting up stack every time, do we need to migrate old stack's content to
new stack?
2. Based on ArmPlatformLib-Full-Boot.png, these 3 stacks's regions didn't
locate in normal dram region.
But, on RealView Eb, they all located in dram region, are they ok?
3. Secure RAM and SRAM
Are they different ram?
4. Secure Firmware's scope
It seems only SEC phase code is defined as secure firmware, and it needs to
setup stack in secure ram, and running in secure mode.
Why not include PEI/DXE/BDS into secure firmware's scope, and the whole
uefi bios runs in secure mode?
best wishes,
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
