The drmemtrace scheduler currently has support for TRACE_MARKER_TYPE_DIRECT_SWITCH but it does not fully model "unscheduled" threads which will not run until explicitly woken up by another thread. This issue covers adding this support through new markers for waiting, resuming, and timeouts.
The drmemtrace scheduler currently has support for TRACE_MARKER_TYPE_DIRECT_SWITCH but it does not fully model "unscheduled" threads which will not run until explicitly woken up by another thread. This issue covers adding this support through new markers for waiting, resuming, and timeouts.