>
> Try simply internal.enums.timing, that should work.
>

To use this, I had to also add 'import enums' to
src/python/m5/internal/__init__.py.  It looks like this completely fixed the
restore problem for the Atomic and Timing CPUs.

When I tried to restore into the O3 CPU, M5 entered simulation, but it died
100,000,000 ticks later with a segmentation fault:

----------OUTPUT------------------------------------
(gdb) run --outdir=$OUTDIR configs/example/fs.py --num-cpus=2 --detailed
--l2cache --caches -r 1
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program: /home/jhestnes/work/public-m5-new/build/ALPHA_FS/m5.debug
--outdir=$OUTDIR configs/example/fs.py --num-cpus=2 --detailed --l2cache
--caches -r 1
[Thread debugging using libthread_db enabled]
M5 Simulator System

Copyright (c) 2001-2008
The Regents of The University of Michigan
All Rights Reserved


M5 compiled Sep 17 2010 11:18:50
M5 revision d19839dbf920+ 7684+ default qtip tip joel/working_changes qbase
M5 started Sep 17 2010 11:19:57
M5 executing on RADLAB-0002
command line: /home/jhestnes/work/public-m5-new/build/ALPHA_FS/m5.debug
--outdir=/home/jhestnes/work/m5/m5out/2010-09-16_mcpat_o3_test-0
configs/example/fs.py --num-cpus=2 --detailed --l2cache --caches -r 1
Script to execute:
Global frequency set at 1000000000000 ticks per second
info: kernel located at:
/home/jhestnes/work/disk-images/binaries/vmlinux_2.6.27-gcc_4.3.4_test64
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
0: system.remote_gdb.listener: listening for remote gdb #1 on port 7001
Switch at curTick count:10000
info: Entering event queue @ 2618511774500.  Starting simulation...
Switched CPUS @ cycle = 2618511784500
Changing memory mode to timing
switching cpus
**** REAL SIMULATION ****
info: Entering event queue @ 2618511784500.  Starting simulation...

Program received signal SIGSEGV, Segmentation fault.
0x0000000000457bd0 in RefCountingPtr (this=0x7fffffffba00, r=...) at
build/ALPHA_FS/base/refcnt.hh:84
84     RefCountingPtr(const RefCountingPtr &r) { copy(r.data); }
(gdb) bt
#0  0x0000000000457bd0 in RefCountingPtr (this=0x7fffffffba00, r=...) at
build/ALPHA_FS/base/refcnt.hh:84
#1  0x0000000000457545 in StaticInstPtr (this=0x7fffffffba00, r=...) at
build/ALPHA_FS/cpu/static_inst.hh:523
#2  0x00000000004f8cf5 in FullO3CPU<O3CPUImpl>::trap (this=0x2318c10,
fault=..., tid=0, inst=...) at build/ALPHA_FS/cpu/o3/cpu.cc:950
#3  0x00000000004f95fe in FullO3CPU<O3CPUImpl>::processInterrupts
(this=0x2318c10, interrupt=...) at build/ALPHA_FS/cpu/o3/cpu.cc:930
#4  0x00000000004d5904 in DefaultCommit<O3CPUImpl>::handleInterrupt
(this=0x231b138) at build/ALPHA_FS/cpu/o3/commit_impl.hh:659
#5  0x00000000004d1381 in DefaultCommit<O3CPUImpl>::commit (this=0x231b138)
at build/ALPHA_FS/cpu/o3/commit_impl.hh:704
#6  0x00000000004cfa0f in DefaultCommit<O3CPUImpl>::tick (this=0x231b138) at
build/ALPHA_FS/cpu/o3/commit_impl.hh:598
#7  0x00000000004ee69d in FullO3CPU<O3CPUImpl>::tick (this=0x2318c10) at
build/ALPHA_FS/cpu/o3/cpu.cc:516
#8  0x00000000004feda8 in FullO3CPU<O3CPUImpl>::TickEvent::process
(this=0x2318d18) at build/ALPHA_FS/cpu/o3/cpu.cc:86
#9  0x00000000005e0bd6 in EventQueue::serviceOne (this=0x10c8920) at
build/ALPHA_FS/sim/eventq.cc:203
#10 0x000000000062570e in simulate (num_cycles=9223372036854775807) at
build/ALPHA_FS/sim/simulate.cc:73
#11 0x000000000041fe80 in _wrap_simulate__SWIG_0 (args=0x1652750) at
build/ALPHA_FS/python/swig/event_wrap.cc:4379
#12 0x000000000042003e in _wrap_simulate (self=0x0, args=0x1652750) at
build/ALPHA_FS/python/swig/event_wrap.cc:4429
#13 0x00007ffff73fd313 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#14 0x00007ffff73fed60 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.6.so.1.0
#15 0x00007ffff73fd0ab in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#16 0x00007ffff73fd928 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#17 0x00007ffff73fed60 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.6.so.1.0
#18 0x00007ffff73fee32 in PyEval_EvalCode () from
/usr/lib/libpython2.6.so.1.0
#19 0x00007ffff73fe0b9 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#20 0x00007ffff73fed60 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.6.so.1.0
#21 0x00007ffff73fd0ab in PyEval_EvalFrameEx () from
/usr/lib/libpython2.6.so.1.0
#22 0x00007ffff73fed60 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.6.so.1.0
#23 0x00007ffff73fee32 in PyEval_EvalCode () from
/usr/lib/libpython2.6.so.1.0
#24 0x00007ffff741cd1c in PyRun_StringFlags () from
/usr/lib/libpython2.6.so.1.0
#25 0x00000000005ebd7a in m5Main (argc=9, argv=0x7fffffffe108) at
build/ALPHA_FS/sim/init.cc:248
#26 0x00000000004097fb in main (argc=9, argv=0x7fffffffe108) at
build/ALPHA_FS/sim/main.cc:57
----------OUTPUT------------------------------------

  Is it possible that these issues are related?

  Thanks,
  Joel

-- 
  Joel Hestness
  PhD Student, Computer Architecture
  Dept. of Computer Science, University of Texas - Austin
  http://www.cs.utexas.edu/~hestness
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to