i#2843 trace cpus: add cpu and timestamp trace markers #2849
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.
Adds a timestamp marker and a cpu marker to the trace buffer header for
each thread's buffer unit output. The timestamp was already in the raw
offline trace format, but now it is in the final trace for both offline and
online as a new marker type. The cpu is completely new and specifies which
core that thread executed on at the granularity of the buffer unit.
Refactors the initial and per-output buffer headers to fix warts in the
tracer: now the initial buffer's timestamp is from output time rather than
thread init time; the initial header is more cleanly skipped for virt2phys;
header uses are more normalized and easier to understand.
Updates the basic_counts tool to separate these new scheduling marks from
kernel transfer and other markers. Updates the corresponding
documentation.
A forthcoming change will update the cache simulator to schedule threads
based on executed cores rather than a thread round-robin scheme.
Issue: #2843