Also, if you want to make sure this is what happens, you can specify "--debug-flag=Exec" before se.py to see the flow of instructions and you should be able to see two different cpu in the output debug file. Then you can compare this against running each benchmark alone on one core and see if the flow of instructions matches.
On 2013-07-17, at 12:59 PM, Zheng Wu <z...@uwaterloo.ca> wrote: > Hi Jordan, > > I believe the se.py script is already setup such that the first program runs > on the first core while the second program run on the second core. Someone > please correct me if I'm wrong!! > > If you look at se.py: > > for i in xrange(np): > if options.smt: > system.cpu[i].workload = multiprocesses > elif len(multiprocesses) == 1: > system.cpu[i].workload = multiprocesses[0] > else: > system.cpu[i].workload = multiprocesses[i] > > The last line should be the one that is invoked assuming you're not using > SMT. Basically the workload for cpu[i] gets assigned to multiprocess[i], > where multiprocess is a list which equals to [.../basicmath_small, > ../search_small]. > > Best, > Zheng Wu > > On 2013-07-17, at 12:49 PM, Jordan Dean <jordan_d...@live.com> wrote: > >> Hello, >> >> I have been in a research program for a few weeks, and am so close to >> making a real breakthrough in my topic but ran into a few major issues. They >> seemed simple at first. Here is what command I am running, most of it is >> just the defaults but just to show it all stays constant when i add cores. >> >> build/X86/gem5.opt configs/example/se.py -c >> ../benchmarks/automotive/basicmath/basicmath_small;../benchmarks/office/stringsearch/search_small >> --clock=2GHz --num-cpus=2 --caches --l2cache --cpu-type=detailed >> --l1d_size=64kB --l1i_size=32kB --l2_size=2MB --l3_size=16MB --l1d_assoc=2 >> --l1i_assoc=2 --l2_assoc=8 --l3_assoc=16 --num-dirs=1 --num-l2caches=1 >> --num-l3caches=1 >> >> >> The most important issue I have, put simply, is how to specify >> basicmath_small to run on the first core, and search_small to run on the >> second. When I run this it just runs them both successively on the first >> core, and stats output is very limited. Definitely not the usual stats.txt >> ran in detailed mode. Once I am passed this point, the next two weeks after >> should be very fulfilling and productive. I look forward to your response. >> >> Thank you, >> Dean >> _______________________________________________ >> gem5-users mailing list >> gem5-users@gem5.org >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
