SynchroTrace - Revision history

Vasil at 05:57, 4 March 2021

2021-03-04T05:57:37Z

← Older revision		Revision as of 01:57, 4 March 2021
Line 52:		Line 52:

	Please follow the included Readme to compile SynchroTrace and run the sample traces for the first time.		Please follow the included Readme to compile SynchroTrace and run the sample traces for the first time.


	~~= Also available at =~~
	~~https://github.com/VANDAL/SynchroTrace-gem5~~

2021-03-04T05:56:48Z

Also available at

← Older revision		Revision as of 01:56, 4 March 2021
Line 55:		Line 55:

	= Also available at =		= Also available at =
	~~http~~://~~dpac~~.~~ece.drexel.edu~~/~~current-research~~-~~projects/synchrotrace/~~		https://github.com/VANDAL/SynchroTrace-gem5

2019-08-12T16:30:33Z

Replay Model:

← Older revision		Revision as of 12:30, 12 August 2019
Line 23:		Line 23:
	Traces are fed into the replay timing model, which acts as an interface into the external architecture models.		Traces are fed into the replay timing model, which acts as an interface into the external architecture models.

	[[File:~~replay_diagram~~.~~jpg\|600px~~\| SynchroTrace Replay]]		[[File:ST_Capture_Replay.png\| SynchroTrace Capture/Replay Flow]]

	~~replay_diagram~~

	The Replay portion of SynchroTrace is comprised of 4 entities:		The Replay portion of SynchroTrace is comprised of 4 entities:

2017-03-02T20:34:03Z

← Older revision		Revision as of 16:34, 2 March 2017
Line 39:		Line 39:
	=Getting SynchroTrace:=		=Getting SynchroTrace:=

	The SynchroTrace Simulation Framework is accessible through GitHub at: https://github.com/VANDAL/SynchroTrace-gem5		The SynchroTrace Simulation Framework is accessible through GitHub at: [https://github.com/VANDAL/SynchroTrace-gem5 git.io/synchrotrace]

	Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.		Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.

2017-02-24T00:49:01Z

Getting SynchroTrace:

← Older revision		Revision as of 20:49, 23 February 2017
Line 39:		Line 39:
	=Getting SynchroTrace:=		=Getting SynchroTrace:=

	The SynchroTrace Simulation Framework is accessible through GitHub at: https://github.com/~~dpac~~-~~vlsi~~		The SynchroTrace Simulation Framework is accessible through GitHub at: https://github.com/VANDAL/SynchroTrace-gem5

	Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.		Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.

2015-05-08T01:17:11Z

← Older revision		Revision as of 21:17, 7 May 2015
Line 1:		Line 1:
	~~<anyweb> http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/ </anyweb>~~

	~~The above page is embedded from Prof. Mark Hempstead's webpage~~


	== SynchroTrace ==		== SynchroTrace ==
Line 58:		Line 54:

	Please follow the included Readme to compile SynchroTrace and run the sample traces for the first time.		Please follow the included Readme to compile SynchroTrace and run the sample traces for the first time.


			= Also available at =
			http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/

2015-04-07T15:51:46Z

← Older revision		Revision as of 11:51, 7 April 2015
Line 1:		Line 1:
	<anyweb> http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/ </anyweb>		<anyweb> http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/ </anyweb>
	~~<anyweb> http://webapps.coe.drexel.edu/forms/computing-for-power-and-energy </anyweb>~~

	The above page is embedded from Prof. Mark Hempstead's webpage		The above page is embedded from Prof. Mark Hempstead's webpage

2015-04-07T15:51:34Z

← Older revision		Revision as of 11:51, 7 April 2015
Line 1:		Line 1:
	<anyweb> http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/ </anyweb>		<anyweb> http://dpac.ece.drexel.edu/current-research-projects/synchrotrace/ </anyweb>
			<anyweb> http://webapps.coe.drexel.edu/forms/computing-for-power-and-energy </anyweb>

	The above page is embedded from Prof. Mark Hempstead's webpage		The above page is embedded from Prof. Mark Hempstead's webpage

2015-04-07T00:14:16Z

Getting SynchroTrace:

← Older revision		Revision as of 20:14, 6 April 2015
Line 47:		Line 47:
	Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.		Currently, there is only a repository for playing the synchronization-aware traces into the external cache and NoC models (Ruby and Garnet). We’ve included a few sample traces to test and explore this code-base. We are currently prepping the capture tool for release very soon.

	The SynchroTrace publication can be found here.		The SynchroTrace publication can be found [[media:SynchroTrace.pdf‎\|here]].

	= Dependencies:=		= Dependencies:=

2015-04-07T00:12:16Z

Replay Model:

← Older revision		Revision as of 20:12, 6 April 2015
Line 27:		Line 27:
	Traces are fed into the replay timing model, which acts as an interface into the external architecture models.		Traces are fed into the replay timing model, which acts as an interface into the external architecture models.

	[[File:replay_diagram.jpg\| SynchroTrace Replay]]		[[File:replay_diagram.jpg\|600px\| SynchroTrace Replay]]

	replay_diagram		replay_diagram