Hi, here is the debug simulation command line: ./build/ARM/gem5.debug --debug-flags=Exec,ExecTicks configs/example/fs.py --maxinsts=10 --machine-type=VExpress_GEM5_V1 --kernel /home/khilji/gem5/m5/system/binaries/vmlinux-aarch32 --disk-image /home/khilji/gem5/m5/system/disks/linux-aarch32-ael.img --dtb-filename /home/khilji/gem5/m5/system/dtb/armv7_gem5_v1_4cpu.dtb --num-cpus=4 --cpu-type=timing --mem-size=512MB --ruby --num-dirs=2 --garnet-network flexible --topology Mesh --mesh-rows 2 --numa-high-bit=28
directory control range1 connection1 directory control range1 connection1 Global frequency set at 1000000000000 ticks per second warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (256 Mbytes) warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (256 Mbytes) info: kernel located at: /home/khilji/gem5/m5/system/binaries/vmlinux-aarch32 Listening for system connection on port 5901 Listening for system connection on port 3457 0: system.remote_gdb.listener: listening for remote gdb #0 on port 7004 0: system.remote_gdb.listener: listening for remote gdb #1 on port 7005 0: system.remote_gdb.listener: listening for remote gdb #2 on port 7006 0: system.remote_gdb.listener: listening for remote gdb #3 on port 7007 warn: ClockedObject: More than one power state change request encountered within the same simulation tick warn: ClockedObject: More than one power state change request encountered within the same simulation tick warn: ClockedObject: More than one power state change request encountered within the same simulation tick warn: ClockedObject: More than one power state change request encountered within the same simulation tick info: Using bootloader at address 0x10 info: Using kernel entry physical address at 0x80008000 info: Loading DTB file: /home/khilji/gem5/m5/system/dtb/armv7_gem5_v1_4cpu.dtb at address 0x88000000 **** REAL SIMULATION **** warn: Existing EnergyCtrl, but no enabled DVFSHandler found. info: Entering event queue @ 0. Starting simulation... 36500: system.cpu0 T0 : @.tmp_kallsyms2.o : mov pc, r7 : IntAlu : D=0x0000000000000010 37500: system.cpu1 T0 : @.tmp_kallsyms2.o : mov pc, r7 : IntAlu : D=0x0000000000000010 38500: system.cpu2 T0 : @.tmp_kallsyms2.o : mov pc, r7 : IntAlu : D=0x0000000000000010 39500: system.cpu3 T0 : @.tmp_kallsyms2.o : mov pc, r7 : IntAlu : D=0x0000000000000010 72500: system.cpu0 T0 : @_start : b : IntAlu : 73500: system.cpu1 T0 : @_start : b : IntAlu : 74500: system.cpu2 T0 : @_start : b : IntAlu : 75500: system.cpu3 T0 : @_start : b : IntAlu : 108500: system.cpu0 T0 : @up_b_offset+4 : mrc r8, r84, #655617 : IntAlu : D=0x0000000080000000 109500: system.cpu1 T0 : @up_b_offset+4 : mrc r8, r84, #655617 : IntAlu : D=0x0000000080000001 110500: system.cpu2 T0 : @up_b_offset+4 : mrc r8, r84, #655617 : IntAlu : D=0x0000000080000002 111500: system.cpu3 T0 : @up_b_offset+4 : mrc r8, r84, #655617 : IntAlu : D=0x0000000080000003 144500: system.cpu0 T0 : @up_b_offset+8 : bics r8, r8, #4278190080 : IntAlu : D=0x0000000000000001 145500: system.cpu1 T0 : @up_b_offset+8 : bics r8, r8, #4278190080 : IntAlu : D=0x0000000000000000 146500: system.cpu2 T0 : @up_b_offset+8 : bics r8, r8, #4278190080 : IntAlu : D=0x0000000000000000 147500: system.cpu3 T0 : @up_b_offset+8 : bics r8, r8, #4278190080 : IntAlu : D=0x0000000000000000 180500: system.cpu0 T0 : @up_b_offset+12 : bxeq : IntAlu : 181500: system.cpu1 T0 : @up_b_offset+12 : bxeq : IntAlu : Predicated False 182500: system.cpu2 T0 : @up_b_offset+12 : bxeq : IntAlu : Predicated False 183500: system.cpu3 T0 : @up_b_offset+12 : bxeq : IntAlu : Predicated False 217500: system.cpu1 T0 : @up_b_offset+16 : mov r8, #1 : IntAlu : D=0x0000000000000001 218500: system.cpu2 T0 : @up_b_offset+16 : mov r8, #1 : IntAlu : D=0x0000000000000001 219500: system.cpu3 T0 : @up_b_offset+16 : mov r8, #1 : IntAlu : D=0x0000000000000001 warn: Replacement policy updates recently became the responsibility of SLICC state machines. Make sure to setMRU() near callbacks in .sm files! 246500: system.cpu0 T0 : @stext : bl : IntAlu : D=0x0000000080008004 253500: system.cpu1 T0 : @up_b_offset+20 : str r8, [r4, #0] : MemWrite : D=0x0000000000000001 A=0x2c002000 254500: system.cpu2 T0 : @up_b_offset+20 : str r8, [r4, #0] : MemWrite : D=0x0000000000000001 A=0x2c002000 255500: system.cpu3 T0 : @up_b_offset+20 : str r8, [r4, #0] : MemWrite : D=0x0000000000000001 A=0x2c002000 306500: system.cpu1 T0 : @up_b_offset+24 : wfi : IntAlu : 308500: system.cpu2 T0 : @up_b_offset+24 : wfi : IntAlu : 310500: system.cpu3 T0 : @up_b_offset+24 : wfi : IntAlu : 318500: system.cpu0 T0 : @__hyp_stub_install : mrs r4, cpsr : IntAlu : D=0x00000000600001d3 319500: system.cpu0 T0 : @__hyp_stub_install+4 : and r4, r4, #31 : IntAlu : D=0x0000000000000013 320500: system.cpu0 T0 : @__hyp_stub_install+8 : adr r5, r1, #172 : IntAlu : D=0x000000008001ae5c 321500: system.cpu0 T0 : @__hyp_stub_install+12 : ldr r6, [r5, #0] : MemRead : D=0x00000000006a9014 A=0x8001ae5c Exiting @ tick 381000 because a thread reached the max instruction count
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
