sravan/system76-coreboot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

libpayload: gdb: Factor out gdb_handle_reentrant_exception() from arm32

Browse Source 
The arm32 GDB architecture code contains a little hack that allows it to
(sort of) correctly deal with a reentrant exception triggered from
within the GDB stub. The main logic for this isn't really arm32 specific
and could be useful for other architectures as well, so factor it out
into a separate function.

Change-Id: I3c6db8cecf1e86bba23de6fd2ac9fdf0cf69d3c6
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/29019
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
Julius Werner
2018-10-10 15:54:10 -07:00
parent 5c0e72ff99
commit 1bfda7293a
3 changed files with 32 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
payloads/libpayload/arch/arm/gdb.c
View File

@@ -39,23 +39,7 @@ static struct exception_state sentinel_exception_state;
static int gdb_exception_hook(u32 type)
{
/*
* If we were not resumed we are in deep trouble here. GDB probably told
* us to do something stupid and caused a reentrant exception. All we
* can do is just blindly send an error code and keep going. Eventually
* GDB will tell us to resume and we return right back to the original
* exception state ("jumping over" all the nested ones).
*/
if (gdb_state.connected && !gdb_state.resumed) {
static const char error_code[] = "E22"; /* EINVAL? */
static const struct gdb_message tmp_reply = {
.buf = (u8 *)error_code,
.used = sizeof(error_code),
.size = sizeof(error_code),
};
gdb_send_reply(&tmp_reply);
gdb_command_loop(gdb_state.signal); /* preserve old signal */
} else {
if (!gdb_handle_reentrant_exception()) {
if (type >= ARRAY_SIZE(type_to_signal) || !type_to_signal[type])
return 0;
exception_state_ptr = &sentinel_exception_state;