Skip to content

Sundry changes to improve DTrace stability on FreeBSD/arm64, with possibly similar affects for other architectures#1

Open
rwatson wants to merge 4 commits intomasterfrom
arm64_dtrace_fixes
Open

Sundry changes to improve DTrace stability on FreeBSD/arm64, with possibly similar affects for other architectures#1
rwatson wants to merge 4 commits intomasterfrom
arm64_dtrace_fixes

Conversation

@rwatson
Copy link
Owner

@rwatson rwatson commented Dec 23, 2020

No description provided.

Don't allow FBT to instrument memcpy().  This is a bit lazy, but avoids
several panic variations I've encountered.  I need to figure out if it
is because memcpy() is being substituted by the compiler, or whether there
is an undesirable explicit call to memcpy() somewhere in DTrace or its
dependencies.
instrumented by FBT.  With this change, we can now instrument all
remaining function entries in the kernel using FBT and not immediately
crash in boring operation.
@rwatson rwatson changed the title Don't call instrumentable nanouptime() from within DTrace probes. Sundry changes to improve DTrace stability on FreeBSD/arm64, with possibly similar affects for other architectures Dec 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant