Hi Max, Did you recompile the model after changing MaxThreads? In terms of debugging, Can you locate the code that populates the fetchprioritylist? Can you double check that a change in MaxThreads is setting up that list correctly?
-Korey On Wed, Sep 26, 2012 at 7:51 AM, Maximilien Breughe < [email protected]> wrote: > Hi, > > I would like to run multiple programs on an inorder core which supports > SMT. > For this I needed to replace MaxThreads = 1 by (e.g.) MaxThreads = 2 in > src/cpu/inorder/pipeline_**traits.hh. > However, running the simulator with smt enabled for an inorder core > results into a Segmentation fault. > Does anyone have an idea? > > To run two instances of "hello world" on an inorder core I use: > build/ALPHA/gem5.opt configs/example/se.py --cmd=tests/test-progs/hello/** > bin/alpha/linux/hello;tests/**test-progs/hello/bin/alpha/**linux/hello > --cpu-type=inorder --caches --smt > > The same command on a "detailed" cpu works fine, but running this command > for an inorder cpu results into a segmentation fault. Gdb told me that > there is a problem on this line: > FirstStage::roundRobin (this=0x27670d0) at build/ALPHA/cpu/inorder/first_* > *stage.cc:255. > This is the line of code causing the problem: > list<ThreadID>::iterator pri_iter = fetchPriorityList->begin(); > > > Kind regards, > > Max > > ______________________________**_________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/**mailman/listinfo/gem5-users<http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users> > -- - Korey
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
