It is working fine for me.
./build/X86_SE_MESI_CMP_directory/m5.fast
./configs/example/ruby_random_test.py -n 4 -l 10000
M5 Simulator System
Copyright (c) 2001-2008
The Regents of The University of Michigan
All Rights Reserved
M5 compiled Mar 23 2011 15:53:38
M5 started Mar 23 2011 15:53:52
M5 executing on mumble-09.cs.wisc.edu
command line: ./build/X86_SE_MESI_CMP_directory/m5.fast
./configs/example/ruby_random_test.py -n 4 -l 10000
Global frequency set at 1000000000 ticks per second
info: Entering event queue @ 0. Starting simulation...
hack: be nice to actually delete the event here
Exiting @ tick 14536941 because Ruby Tester completed
On Wed, 23 Mar 2011, Nilay Vaish wrote:
I will try to bisect this.
--
Nilay
On Wed, 23 Mar 2011, Arkaprava Basu wrote:
Hi Lisa and Nilay,
Thanks for the response. Following is the tip of my repo
changeset: 8174:e21f6e70169e
tag: tip
user: Nilay Vaish<ni...@cs.wisc.edu>
date: Tue Mar 22 06:41:54 2011 -0500
summary: Ruby: Remove CacheMsg class from SLICC
So this is after Nilay's patch for CacheMsg. And yes it did not tun for
10-15 mins, died immediately. The architecture should not matter for
random_tester. I am not sure then why its breaking. Seems like something
broken.
Thanks
Arka
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
