Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i#5843 scheduler: Add replay of the as-traced schedule #6045

Merged
merged 6 commits into from
May 15, 2023

Conversation

derekbruening
Copy link
Contributor

@derekbruening derekbruening commented May 12, 2023

Adds replay of the as-traced schedule using the cpu_schedule.zip file written by raw2trace. That file is converted into the record+replay format for dynamic schedules and the existing replay code leveraged.

This implements as-traced cpu-oriented parallel iteration in the scheduler which is part of #5694. Adding analysis tool support for this will be done separately.

Updates all replays (whether as-traced or as-previously) to consider DEPENDENCY_TIMESTAMPS to indicate whether to have one output wait if it gets ahead of another's timestamp.

Removes STATUS_IDLE since we always use STATUS_WAIT. We're between releases so we can delete from the public enum for this still-under-development component without worrying about binary compatibility.

Adds a missing check for output count mismatches on as-previously replay.

Adds unit tests of synthetic and from-file replay.

Issue: #5843, #5694

Adds replay of the as-traced schedule using the cpu_schedule.zip file
written by raw2trace.  That file is converted into the record+replay
format for dynamic schedules and the existing replay code leveraged.

This implements as-traced cpu-oriented parallel iteration in the
scheduler which is part of #5694.  Adding analysis tool support for
this will be done separately.

Updates all replays (whether as-traced or as-previously) to consider
DEPENDENCY_TIMESTAMPS to indicate whether to have one output wait if
it gets ahead of another's timestamp.

Adds a missing check for output count mismatches on as-previously
replay.

Issue: #5843, #5694
… so we can delete w/o affecting compatibility
clients/drcachesim/scheduler/scheduler.cpp Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Outdated Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Outdated Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Outdated Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Outdated Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Outdated Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Show resolved Hide resolved
clients/drcachesim/scheduler/scheduler.cpp Show resolved Hide resolved
@derekbruening derekbruening merged commit 2c5b33a into master May 15, 2023
@derekbruening derekbruening deleted the i5843-scheduler-as-traced branch May 15, 2023 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants