summaryrefslogtreecommitdiff
path: root/BaseTools/Source
diff options
context:
space:
mode:
authorLevi Yun <yeoreum.yun@arm.com>2024-08-21 01:59:00 +0100
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2025-01-17 14:55:42 +0000
commit7340a4b63a993151817faa0adabebfeb007d16c1 (patch)
tree072cee7320da46dc8ffe20c92ef3059b4fd06c4d /BaseTools/Source
parent697549465512b4a50d9e2d6f8d28d78b6c7c92e1 (diff)
downloadedk2-7340a4b63a993151817faa0adabebfeb007d16c1.zip
edk2-7340a4b63a993151817faa0adabebfeb007d16c1.tar.gz
edk2-7340a4b63a993151817faa0adabebfeb007d16c1.tar.bz2
StandaloneMmPkg: Apply embedded stack in StandaloneMmEntryPoint
There are 2 communication interfaces between the SPMC and StandaloneMM 1. SpmMM 2. FF-A When SpmMM is enabled, TF-A acts as the SPMC at EL3 and the stack is setup by TF-A for use by StandaloneMm. However, when FF-A is enabled, the SPMC does not setup the stack for StandaloneMm and it is expected that the StandaloneMm code will setup its own stack. Therefore, reserve an area in the data region for use as the stack for StandaloneMM. This stack will be used in both the scenarios described above, i.e. when either SpmMM or FF-A is enabled. Although the stack is reserved from the data section which is expected to be Read-Write enabled, when TF-A maps the StandaloneMM binary into the DRAM it configures the entire StandaloneMM memory as Read-Only. Therefore, before the stack can be utilised, the PE Coff sections need to be scanned to change the the stack region from Read-Only to Read-Write. Signed-off-by: Levi Yun <yeoreum.yun@arm.com>
Diffstat (limited to 'BaseTools/Source')
0 files changed, 0 insertions, 0 deletions