2e0bca011a
To avoid trampling over interesting exception artifacts on the real stack, our arm64 systems switch to a separate exception stack when entering an exception handler. We don't want that to use up too much SRAM so we just set it to 512 bytes. I mean it just prints a bunch of registers, how much stack could it need, right? Quite a bit it turns out. The whole vtxprintf() call stack goes pretty deep, and aarch64 generally seems to be very generous with stack space. Just the varargs handling seems to require 128 bytes for some reason, and the other stuff adds up too. In the end the current implementation takes 1008 bytes, so bump the exception stack size to 2K to make sure it fits. Change-Id: I910be4c5f6b29fae35eb53929c733a1bd4585377 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37464 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Hung-Te Lin <hungte@chromium.org> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile.inc | ||
| cache.c | ||
| coreboot.c | ||
| cpu.S | ||
| dummy_media.c | ||
| exception.c | ||
| exception_asm.S | ||
| gdb.c | ||
| head.S | ||
| libpayload.ldscript | ||
| main.c | ||
| memcpy.S | ||
| memmove.S | ||
| memset.S | ||
| mmu.c | ||
| selfboot.c | ||
| sysinfo.c | ||
| timer.c | ||
| util.S | ||
| virtual.c | ||