I don't think if that command works or doesn't work is pertinent to this problem. Why does not setting test sys.switch_cpu fix it?
Ali On Jan 2, 2012, at 9:02 AM, Nilay wrote: > > Ali, do you expect the following command to work -- > > build/X86_FS/gem5.opt configs/example/fs.py --kernel > x86_64-vmlinux-2.6.22.9 -s -w 100000 --detailed --caches > > This also results in the same error as before -- > > panic: Pio port of system.switch_cpus_1.interrupts not connected to anything! > @ cycle 0 > [init:build/X86_FS/dev/io_device.cc, line 74] > Memory Usage: 307580 KBytes > Program aborted at cycle 0 > Aborted > > > Assume I am not doing any thing wrong. Since switch_cpus.interrupts is a > Pio Device, its init() function will be called, and similarly for > switch_cpus_1.interrupts. I think these would be connected only after the > cpus that the system starts with are done. > > -- > Nilay _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
