Docker workflow for STF trace generation #264
Open
Conversation
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
klingaard
reviewed
Jul 13, 2025
vinicius-r-silva
force-pushed
the
vinicius-r-silva/spike-stf-dockerfile
branch
from
511193a to
b1a5e8f
Compare
arupc
approved these changes
Jul 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new folder, docker_stf_trace_gen, as part of the ongoing Workload Analysis Flow mentorship. It includes:
The current workflow does not yet include the commands to produce STF files. These will be added in a future PR. For now it only includes the basis for the documentation and the Dockerfile with the necessary tools.