summaryrefslogtreecommitdiff
path: root/payloads/libpayload/README
diff options
context:
space:
mode:
authorFelix Held <felix-coreboot@felixheld.de>2021-11-02 17:15:58 +0100
committerFelix Held <felix-coreboot@felixheld.de>2021-11-03 18:37:28 +0000
commit28a0a14b5b4262cc0278ba348cccede9627d7408 (patch)
tree370c932475b45b6d06d9e54916bb81b4e27b4c1b /payloads/libpayload/README
parentc435038c55e4a5db68df8e070e756d5a76a5b3ef (diff)
soc/amd/*/cpu: handle mp_init_with_smm failure
When the mp_init_with_smm call returns a failure, coreboot can't just continue with the initialization and boot process due to the system being in a bad state. Ignoring the failure here would just cause the boot process failing elsewhere where it may not be obvious that the failed multi-processor initialization step was the root cause of that. I'm not 100% sure if calling do_cold_reset or calling die_with_post_code is the better option here. Calling do_cold_reset likely here would likely result in a boot-failure loop, so I call die_with_post_code here. BUG=b:193809448 Signed-off-by: Felix Held <felix-coreboot@felixheld.de> Change-Id: Ifeadffb3bae749c4bbd7ad2f3f395201e67d9e28 Reviewed-on: https://review.coreboot.org/c/coreboot/+/58859 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Raul Rangel <rrangel@chromium.org>
Diffstat (limited to 'payloads/libpayload/README')
0 files changed, 0 insertions, 0 deletions