config: Add options to take/resume from SimPoint checkpoints

Information
Submitter:	Andreas Hansson
Repository:	gem5
Branch:	default
Bugs:
Depends On:
Reviewers
Groups:	Default
People:

Description

Changeset 10606:3a4e0cb7ffe6
---------------------------
config: Add options to take/resume from SimPoint checkpoints

More documentation at http://gem5.org/Simpoints

Steps to profile, generate, and use SimPoints with gem5:

1. To profile workload and generate SimPoint BBV file, use the
following option:

--simpoint-profile --simpoint-interval <interval length>

Requires single Atomic CPU and fastmem.
<interval length> is in number of instructions.

2. Generate SimPoint analysis using SimPoint 3.2 from UCSD.
(SimPoint 3.2 not included with this flow.)

3. To take gem5 checkpoints based on SimPoint analysis, use the
following option:

--take-simpoint-checkpoint=<simpoint file path>,<weight file
path>,<interval length>,<warmup length>

<simpoint file> and <weight file> is generated by SimPoint analysis
tool from UCSD. SimPoint 3.2 format expected. <interval length> and
<warmup length> are in number of instructions.

4. To resume from gem5 SimPoint checkpoints, use the following option:

--restore-simpoint-checkpoint -r <N> --checkpoint-dir <simpoint
checkpoint path>

<N> is (SimPoint index + 1). E.g., "-r 1" will resume from SimPoint
#0.

Testing Done

Issue Summary

Description	From	Last Updated	Status
Can you explain why we need this separate option for restoring from a checkpoint taken using the take-simpoint-checkpoints?	Nilay Vaish	Dec. 5, 2014, 12:36 a.m.	Resolved

I suggest the additions being made to the Simulation.py file be made by creating new functions.
I think the run function is already too big and confusing.

Dam Sunwoo Dec. 2, 2014, 1:56 p.m. (Dec. 2, 2014, 1:56 p.m.)

I can work on cleaning up the patch by creating new functions as suggested.

configs/common/Options.py (Diff revision 1)

Can you explain why we need this separate option for restoring from a checkpoint taken using the take-simpoint-checkpoints?

Show all issues

Ali Saidi Nov. 28, 2014, 7:47 p.m. (Nov. 28, 2014, 7:47 p.m.)

The simpoint checkpoint names include more information about the source of the checkpoint that needs to parsed.

mike upton Dec. 2, 2014, 12:41 p.m. (Dec. 2, 2014, 12:41 p.m.)

It may be obvious, but generating the checkpoint takes one input plus the simpoint file and creates N checkpoints. The restore command then can run all of the N checkpoints in parallel, but each one needs to know which sample to run.

I have been using the patch and it works well for me so far...

Dam Sunwoo Dec. 2, 2014, 1:56 p.m. (Dec. 2, 2014, 1:56 p.m.)

As Ali suggested, the restoring needs information on the SimPoints, such as the warmup period specified while taking the SimPoint checkpoints. Not using the exact warmup period will result in inaccurate simulation. To prevent user error, we added a separate option that takes care of that part.

Description:

~		Changeset 10548:abc6a8156083
	~	Changeset 10595:76a699dee100

		config: Add options to take/resume from SimPoint checkpoints

		More documentation at http://gem5.org/Simpoints

		Steps to profile, generate, and use SimPoints with gem5:

		To profile workload and generate SimPoint BBV file, use the following option:

		--simpoint-profile --simpoint-interval <interval length>

		Requires single Atomic CPU and fastmem.
		<interval length> is in number of instructions.

		Generate SimPoint analysis using SimPoint 3.2 from UCSD. (SimPoint 3.2 not included with this flow.)
		To take gem5 checkpoints based on SimPoint analysis, use the following option:

		--take-simpoint-checkpoint=<simpoint file path>,<weight file
		path>,<interval length>,<warmup length>

		<simpoint file> and <weight file> is generated by SimPoint analysis
		tool from UCSD. SimPoint 3.2 format expected. <interval length> and
		<warmup length> are in number of instructions.

		To resume from gem5 SimPoint checkpoints, use the following option:

		--restore-simpoint-checkpoint -r <N> --checkpoint-dir <simpoint
		checkpoint path>

		<N> is (SimPoint index + 1). E.g., "-r 1" will resume from SimPoint

		0.

Diff:

Revision 2 (+190 -2)

Show changes

	configs/common/Options.py
	configs/common/Simulation.py
	configs/example/fs.py

Description:

~		Changeset 10595:76a699dee100
	~	Changeset 10606:3a4e0cb7ffe6

		config: Add options to take/resume from SimPoint checkpoints

		More documentation at http://gem5.org/Simpoints

		Steps to profile, generate, and use SimPoints with gem5:

		To profile workload and generate SimPoint BBV file, use the following option:

		--simpoint-profile --simpoint-interval <interval length>

		Requires single Atomic CPU and fastmem.
		<interval length> is in number of instructions.

		Generate SimPoint analysis using SimPoint 3.2 from UCSD. (SimPoint 3.2 not included with this flow.)
		To take gem5 checkpoints based on SimPoint analysis, use the following option:

		--take-simpoint-checkpoint=<simpoint file path>,<weight file
		path>,<interval length>,<warmup length>

		<simpoint file> and <weight file> is generated by SimPoint analysis
		tool from UCSD. SimPoint 3.2 format expected. <interval length> and
		<warmup length> are in number of instructions.

		To resume from gem5 SimPoint checkpoints, use the following option:

		--restore-simpoint-checkpoint -r <N> --checkpoint-dir <simpoint
		checkpoint path>

		<N> is (SimPoint index + 1). E.g., "-r 1" will resume from SimPoint

		0.

Diff:

Revision 3 (+192 -2)

Show changes

	configs/common/Options.py
	configs/common/Simulation.py
	configs/example/fs.py

You have a pending review.

Review Board 2.0.15

This change has been marked as submitted.

Screenshots

Files

Issue Summary

Description:

Changeset 10548:abc6a8156083

Changeset 10595:76a699dee100

0.

Diff:

Description:

Changeset 10595:76a699dee100

Changeset 10606:3a4e0cb7ffe6

0.

Diff:

Status: Closed (submitted)