summaryrefslogtreecommitdiffstats
path: root/gccdeps.py
diff options
context:
space:
mode:
authorRobert Watson <rwatson@FreeBSD.org>2021-01-09 08:38:11 +0000
committerSebastian Huber <sebastian.huber@embedded-brains.de>2021-11-15 08:56:54 +0100
commit4b384f318cfadddf5726dd6997a2b2d91fd2b6c9 (patch)
tree636c09bd811c1ba944fcac5f2be7b9169c943d90 /gccdeps.py
parentRemove double-calls to tc_get_timecount() (diff)
downloadrtems-4b384f318cfadddf5726dd6997a2b2d91fd2b6c9.tar.bz2
Changes that improve DTrace FBT reliability
on freebsd/arm64: - Implement a dtrace_getnanouptime(), matching the existing dtrace_getnanotime(), to avoid DTrace calling out to a potentially instrumentable function. (These should probably both be under KDTRACE_HOOKS. Also, it's not clear to me that they are correct implementations for the DTrace thread time functions they are used in .. fixes for another commit.) - Don't allow FBT to instrument functions involved in EL1 exception handling that are involved in FBT trap processing: handle_el1h_sync() and do_el1h_sync(). - Don't allow FBT to instrument DDB and KDB functions, as that makes it rather harder to debug FBT problems. Prior to these changes, use of FBT on FreeBSD/arm64 rapidly led to kernel panics due to recursion in DTrace. Reliable FBT on FreeBSD/arm64 is reliant on another change from @andrew to have the aarch64 instrumentor more carefully check that instructions it replaces are against the stack pointer, which can otherwise lead to memory corruption. That change remains under review. MFC after: 2 weeks Reviewed by: andrew, kp, markj (earlier version), jrtc27 (earlier version) Differential revision: https://reviews.freebsd.org/D27766
Diffstat (limited to 'gccdeps.py')
0 files changed, 0 insertions, 0 deletions