gem5/configs/example
Andreas Hansson 88554790c3 Mem: Use cycles to express cache-related latencies
This patch changes the cache-related latencies from an absolute time
expressed in Ticks, to a number of cycles that can be scaled with the
clock period of the caches. Ultimately this patch serves to enable
future work that involves dynamic frequency scaling. As an immediate
benefit it also makes it more convenient to specify cache performance
without implicitly assuming a specific CPU core operating frequency.

The stat blocked_cycles that actually counter in ticks is now updated
to count in cycles.

As the timing is now rounded to the clock edges of the cache, there
are some regressions that change. Plenty of them have very minor
changes, whereas some regressions with a short run-time are perturbed
quite significantly. A follow-on patch updates all the statistics for
the regressions.
2012-10-15 08:10:54 -04:00
..
fs.py Mem: Use cycles to express cache-related latencies 2012-10-15 08:10:54 -04:00
memtest.py Configs: Fix memtest cache latency to match new parameters 2012-09-27 08:59:25 -04:00
ruby_direct_test.py ruby: changes how Topologies are created 2012-07-10 22:51:53 -07:00
ruby_fs.py ruby: changes how Topologies are created 2012-07-10 22:51:53 -07:00
ruby_mem_test.py Mem: Make SimpleMemory single ported 2012-07-12 12:56:13 -04:00
ruby_network_test.py ruby: changes how Topologies are created 2012-07-10 22:51:53 -07:00
ruby_random_test.py ruby: remove the cpu assumptions for the random tester 2012-07-10 22:51:54 -07:00
se.py Configs: SE script fix for Alpha and Ruby simulations 2012-09-28 09:35:25 -04:00