-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Currently Supported:
perf sched record -- sleep 10
perf replay
New:
perf sched record -- sleep 10
perf replay
Means, we still support the old format, why not!?
But now the new things comes into play:
perf sched record -- sleep 10
perf replay --intermediate-generate <outputfilename.dat>
This generated a file, according to issue #10
To replay this newly generated file, a new subcommand can be used:
perf replay --intermediate-use <outputfilename.dat>
Both commands are identical, (except, if the intermediate file is modified, this are different, sure):
perf replay
# is identical to
perf replay --intermediate-generate <outputfilename.dat>
perf replay --intermediate-use <outputfilename.dat>
Normally, the user will edit <outputfilename.dat>, remove some tasks, tweak them or whatever.
It is also possible to generate a <outputfilename.dat> by hand, without recording events all togehter, the examples in #10 are perfectly fines examples.
There are some additional subcommends to tweak the output, like:
perf sched record -- sleep 10
perf replay --intermediate-generate <outputfilename.dat> --intermediate-remove-kernel-task --intermediate-ignore-migration
These kinds of option modify the generated <outputfilename.dat> file. This can be done manually too (e.g. open the editor, modify the places in the file), but because some changes to the file are often done, the additional helper option will do this automatically.