Repository navigation
feat(ktrace): added ktrace-decode to turn a .ktrace recording into a SQLite database - #349
Merged
Merged
Conversation
…with trace readers
… a SQLite database
…d list in the format header
|
This PR is too large for Bugbot to review. It changes 111,256 lines and 4,078,421 characters. Split the change into smaller pull requests to get a review. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
ktrace-decode FILE -o DBruns on StelluxOS and writes a SQLite database:session,cpusandhealthtables, plus one table per event built from field lists in the format header. A compile-time check ties each list to its payload struct, so a new event needs no decoder change and the two cannot drift apart.kernel/trace/ktrace_format.h, which userland includes as<stlx/ktrace_format.h>, and SQLite 3.53.4 is vendored aslibsqlite3.