That's correct...although at this point I'm not too against putting a hacky solution in the InOrderFetchUnit that says "if alpha && name=hwrei", mark as a control instruction.
That patch is really short and I was hoping an elegant solution would fall from the sky for me...but it hasn't so far! :) -Korey On Tue, Feb 26, 2013 at 6:38 AM, Ali Saidi <[email protected]> wrote: > ** > > If memory serves the change breaks the o3 cpu for Alpha. > > > > Ali > > > > On 26.02.2013 08:41, Anthony Gutierrez wrote: > > Can we push that patch out? > > Anthony Gutierrez > http://web.eecs.umich.edu/~atgutier > > > On Tue, Feb 26, 2013 at 8:39 AM, WonSeob Jeong <[email protected]>wrote: > >> Hi, Korey >> >> Thank you for your help! >> I applied hwrei patch and it works fine. >> >> Won Seob Jeong >> >> >> On 02/26/2013 04:28 AM, Korey Sewell wrote: >> >> Hi, >> Make sure you use the "hwrei" patch that should be on the review board. >> That helps the inorder model work w/FS mode. >> >> -Korey >> >> On Fri, Feb 22, 2013 at 3:14 AM, WonSeob Jeong <[email protected]>wrote: >> >>> Hi all, >>> >>> I tried to boot linux with Alpha In-Order CPU model but, it didn't work. >>> The simulation ended with this messages. >>> >>> >>> gem5 Simulator System. http://gem5.org >>> gem5 is copyrighted software; use the --copyright option for details. >>> >>> gem5 compiled Feb 22 2013 18:41:14 >>> gem5 started Feb 22 2013 18:43:16 >>> gem5 executing on >>> command line: build/ALPHA/gem5.opt configs/example/fs.py --caches >>> --cpu-type=inorder >>> Global frequency set at 1000000000000 ticks per second >>> info: kernel located at: >>> /gem5_test/sys_files/m5_system_2.0b3/binaries/vmlinux >>> Listening for system connection on port 3456 >>> 0: system.tsunami.io.rtc: Real-time clock set to Thu Jan 1 >>> 00:00:00 2009 >>> 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7000 >>> **** REAL SIMULATION **** >>> info: Entering event queue @ 0. Starting simulation... >>> 17115489257812500: system.terminal: attach terminal 0 >>> gem5.opt: build/ALPHA/sim/simulate.cc:68: SimLoopExitEvent* >>> simulate(Tick): Assertion `curTick() <= mainEventQueue.nextTick() && "event >>> scheduled in the past"' failed. >>> Program aborted at cycle 9223372000000000000 >>> Aborted (core dumped) >>> >>> >>> However, other CPU models, for example AtomicSimple and O3, work very >>> well. >>> And I can run hello binary which in tests directory on se mode with >>> In-Order CPU. >>> >>> I used gem5-stable version and Full-System Stuff for Alpha which I can >>> download at gem5.org/Download >>> >>> What should I do to fix this problem? >>> >>> Thank you. >>> >>> >>> _______________________________________________ >>> gem5-users mailing list >>> [email protected] >>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> >> >> >> -- >> - Korey >> >> _______________________________________________ >> gem5-users mailing >> [email protected]http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >> >> >> _______________________________________________ >> gem5-users mailing list >> [email protected] >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > _______________________________________________ > gem5-users mailing > [email protected]http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > > _______________________________________________ > gem5-users mailing list > [email protected] > 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
