drmemtrace API is_record_kernel() fails for live injected kernel sequences #7375
Assignees
Labels
Comments
derekbruening
added a commit
that referenced
this issue
Mar 19, 2025
Adds state to the scheduler's output stream to track kernel sequences so that is_record_kernel() works properly for live kernel sequence insertions. Augments the kernel unit tests with checks of is_record_kernel() which fail without the fix. Fixes #7375
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The drmemtrace stream API routine is_record_kernel() is only implemented in the reader_t layer, where it looks for kernel sequence markers. It works on core-sharded-on-disk traces or other traces where the kernel sequences are stored inside the trace files. But when the sequences are dynamically injected, it fails during that live run. This breaks my intended usage in schedule_stats for #7355.
The text was updated successfully, but these errors were encountered: