poc: use frame pointer unwinding for go arm64 #241
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was mostly a learning project for me. I now understand the eBPF unwinding code and coredump testing infrastructure a lot better (it's very cool). More work would be needed to turn this into a proper patch. The way it's currently implemented doesn't really provide any benefits, but I think in theory frame pointer unwinding could greatly decrease the amount of stack delta memory needed when dealing with large Go applications. For now I don't plan to continue with this, but I'm uploading this patch in case somebody else feels inspired to continue at some point ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE
This was mostly a learning project for me. I now understand the eBPF unwinding code and coredump testing infrastructure a lot better (it's very cool).
More work would be needed to turn this into a proper patch. The way it's currently implemented doesn't really provide any benefits, but I think in theory frame pointer unwinding could greatly decrease the amount of stack delta memory needed when dealing with large Go applications. (I think ... I might be wrong on this tho)
For now I don't plan to continue with this, but I'm uploading this patch in case somebody else feels inspired to continue at some point ...