You also have to build a binary that supports ruby, like ALPHA_FS_MOESI_hammer. If you can't get that to work, try ALPHA_SE_MOESI_hammer and run one of the ALPHA_SE test workloads... the workload you run doesn't really matter that much as long as it's long enough to get a meaningful profile.
Steve On Thu, Nov 4, 2010 at 7:17 AM, Nilay Vaish <[email protected]> wrote: > I tried running ruby_fs.py, below is the error message that I received. I > don't think there is any documentation or mailing list discussion on how to > run ruby_fs.py. To me it seems that some parameter relating to the DMA > controller is missing from the command I tried out. > > -- > Nilay > > > ./build/ALPHA_FS/m5.prof ./configs/example/ruby_fs.py -n 1 --detailed > --caches --l2cache -F 5000000000M5 Simulator System > > Copyright (c) 2001-2008 > The Regents of The University of Michigan > All Rights Reserved > > > M5 compiled Nov 3 2010 18:10:26 > M5 revision 3b2f82286e5d 7724 default WarnPatch qtip tip > M5 started Nov 4 2010 08:50:01 > M5 executing on scamorza.cs.wisc.edu > command line: ./build/ALPHA_FS/m5.prof ./configs/example/ruby_fs.py -n 1 > --detailed --caches --l2cache -F 5000000000 > Error: could not create sytem for ruby protocol MI_example > Traceback (most recent call last): > File "<string>", line 1, in ? > File "/scratch/nilay/GEM5/sibling/src/python/m5/main.py", line 359, in > main > exec filecode in scope > File "./configs/example/ruby_fs.py", line 117, in ? > system._dma_devices) > File "/scratch/nilay/GEM5/sibling/configs/ruby/Ruby.py", line 69, in > create_system > (cpu_sequencers, dir_cntrls, all_cntrls) = \ > File "<string>", line 0, in ? > File "/scratch/nilay/GEM5/sibling/configs/ruby/MI_example.py", line 138, > in create_system > system.dma_cntrl.dma_sequencer.port = dma_device.dma > File "/scratch/nilay/GEM5/sibling/src/python/m5/SimObject.py", line 586, > in __getattr__ > raise AttributeError, "object '%s' has no attribute '%s'" \ > AttributeError: object 'LinuxAlphaSystem' has no attribute 'dma_cntrl' > > > > On Wed, 3 Nov 2010, Steve Reinhardt wrote: > > Ah, the issue is that you're using the old M5 memory hierarchy and not >> Ruby. You need to run one of the Ruby versions, and use ruby_fs.py >> instead >> of fs.py. >> >> Steve >> >> _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
