/tf-a-ffa_el3_spmc/lib/stack_protector/ |
A D | stack_protector.mk | 15 TF_CFLAGS += -fno-stack-protector
|
/tf-a-ffa_el3_spmc/plat/arm/board/arm_fpga/ |
A D | build_axf.ld.S | 36 *bl31.elf(.stack)
|
/tf-a-ffa_el3_spmc/drivers/renesas/common/pwrc/ |
A D | pwrc.h | 71 extern uint32_t rcar_pwrc_switch_stack(uintptr_t jump, uintptr_t stack,
|
A D | pwrc.c | 688 uintptr_t stack = (uintptr_t) (DEVICE_SRAM_STACK_BASE + in rcar_pwrc_set_suspend_to_ram() local 699 rcar_pwrc_switch_stack(jump, stack, NULL); in rcar_pwrc_set_suspend_to_ram()
|
/tf-a-ffa_el3_spmc/docs/plat/arm/juno/ |
A D | index.rst | 16 stack that includes TF-A. This version of TF-A is tested with pre-built 17 `Linaro release software stack`_ version 20.01. You can alternatively 18 build the software stack yourself by following the 19 `Juno platform software user guide`_. Once you prepare the software stack 28 a single FIP binary. It assumes that a Linaro release software stack has been 246 .. _Linaro release software stack: http://releases.linaro.org/members/arm/platforms/
|
/tf-a-ffa_el3_spmc/lib/compiler-rt/builtins/ |
A D | assembly.h | 48 #define NO_EXEC_STACK_DIRECTIVE .section .note.GNU-stack,"",%progbits
|
/tf-a-ffa_el3_spmc/docs/security_advisories/ |
A D | security-advisory-tfv-7.rst | 58 This approach permanently mitigates the entire software stack and no additional 87 approach will effectively permanently mitigate the entire software stack, since
|
A D | security-advisory-tfv-8.rst | 29 ``x0`` to ``x3`` are not part of the CPU context saved on the stack. 38 CPU context stored on the stack. This includes registers ``x0`` to ``x3``, as
|
/tf-a-ffa_el3_spmc/docs/plat/arm/fvp-ve/ |
A D | index.rst | 27 - Obtain arm toolchain. The software stack has been verified with linaro 6.2
|
/tf-a-ffa_el3_spmc/plat/renesas/common/ |
A D | plat_pm.c | 39 extern void rcar_pwrc_restore_generic_timer(uint64_t *stack);
|
/tf-a-ffa_el3_spmc/services/spd/trusty/ |
A D | trusty.c | 170 uint64_t handler, uint64_t stack) in trusty_set_fiq_handler() argument 182 ctx->fiq_handler_sp = stack; in trusty_set_fiq_handler()
|
/tf-a-ffa_el3_spmc/docs/plat/ |
A D | stm32mp1.rst | 129 - ``ENABLE_STACK_PROTECTOR``: To enable the stack protection.
|
/tf-a-ffa_el3_spmc/docs/components/ |
A D | exception-handling.rst | 62 rest of the handling to a dedicated software stack running at lower Secure 66 processing of the error to dedicated software stack running at lower secure 95 priority levels as applicable for the Secure software stack. It then assigns the 132 stack—priority levels stack up in strictly increasing fashion, and need to be
|
A D | sdei.rst | 311 written in C: compilers typically adjust the stack frame at the beginning and 343 /* Save link register whilst maintaining stack alignment */
|
A D | secure-partition-manager-mm.rst | 33 The following diagram illustrates the corresponding software stack: 38 centres and enterprise servers) the secure software stack typically does not 72 Armv8-A software stack. A single or multiple Secure Partitions provide secure 477 A non-zero value will indicate that the SPM has initialised the stack pointer
|
A D | secure-partition-manager.rst | 115 Sample reference stack 164 stack. 165 - The reference software stack uses FEAT_PAuth (formerly Armv8.3-PAuth) and
|
/tf-a-ffa_el3_spmc/docs/ |
A D | change-log.rst | 188 - Added support for stack protector 547 - Avoid duplicates in extension stack 621 - Do not keep mmc_device_info in stack 631 - Do not keep mmc_device_info in stack 634 - Do not keep mmc_device_info in stack 833 - Added support for stack protection 1361 - arm/corstone700: Add support for mhuv2 and stack protector 1677 - el3_runtime: Fix stack pointer maintenance on EA handling path, 1797 - Add support for default stack-protector flag 3392 - Added support for GCC stack protection. A new build option [all …]
|
/tf-a-ffa_el3_spmc/docs/getting_started/ |
A D | porting-guide.rst | 41 each BL stage to correctly port the firmware stack. They are categorized as 115 Defines the normal stack memory available to each CPU. This constant is used 960 This function sets the current stack pointer to the normal memory stack that 962 stack for the primary CPU, the UP version of the function is used. The size 963 of the stack allocated to each CPU is specified by the platform defined 978 This function returns the base address of the normal memory stack that 980 stack for the primary CPU, the UP version of the function is used. The size 981 of the stack allocated to each CPU is specified by the platform defined 1044 it has restrictions for stack usage and it can use the registers x0 - x17 as 1123 when the stack protector is enabled with ENABLE_STACK_PROTECTOR. A predictable [all …]
|
A D | build-options.rst | 295 - ``ENABLE_STACK_PROTECTOR``: String option to enable the stack protection 297 default value is set to "none". "strong" is the recommended stack protection 298 level if this feature is desired. "none" disables the stack protection. For 731 tagging for stack or not. It accepts 2 values: ``yes`` and ``no``. The
|
A D | psci-lib-integration-guide.rst | 163 - The C runtime environment must be setup and stack initialized 282 - Invalidates the stack and enables the data cache.
|
/tf-a-ffa_el3_spmc/ |
A D | Makefile | 221 TF_CFLAGS += -mmemtag-stack
|
/tf-a-ffa_el3_spmc/docs/threat_model/ |
A D | threat_model_spm.rst | 444 | | stack protector, pointer authentication, BTI, XN, |
|
A D | threat_model.rst | 416 | | stack dumps. This information is useful when |
|
/tf-a-ffa_el3_spmc/docs/design/ |
A D | firmware-design.rst | 242 bit. Alignment and stack alignment checking is enabled by setting the 984 framework finally sets up the execution stack for the handler, and invokes the 988 before restoring the stack and CPU state and returning from the original SMC. 1177 A dedicated per-CPU crash stack is maintained by BL31 and this is retrieved via 1472 C run time. Therefore it must follow AAPCS, and must not use stack. 1482 must follow AAPCS and may use stack.
|
/tf-a-ffa_el3_spmc/docs/process/ |
A D | coding-guidelines.rst | 232 call stack.
|