I tried to use only 4 core with the 2.6.28.4.smp kernel and even then I am getting the below errors from gem5. I think the current gem5 version is not capable to run the linux kernel 2.6.28.4.smp (from kernel.org or parsec.m5). Hence, please let me know what needful to be done to run the 2.6.28.4.smp kernel in gem5.
./build/X86/gem5.opt configs/example/fs.py --cpu-type=TimingSimpleCPU --script=script/blackscholes_4c_simsmall.rcS --num-cpus=4 --ruby --mesh-rows=2 --network=garnet2.0 --topology=Mesh_XY --caches --l2cache --l2_size=512kB --num-dirs=4 --num-l2=4 --l1d_size=32kB --l1i_size=32kB --l1d_assoc=2 --l1i_assoc=2 --kernel=/home1/x/3RDCOPY/gem5/X86/binaries/x86_64-vmlinux-2.6.28.4.smp --disk-image=/home1/x/3RDCOPY/gem5/X86/disks/x86root.img kernel BUG at arch/x86/kernel/xsave.c:323! warn: x86 cpuid family 0x0000: unimplemented function 13 Kernel panic - not syncing: Attempted to kill the idle task! ------------[ cut here ]------------ WARNING: at kernel/smp.c:333 smp_call_function_mask+0x1de/0x250() Modules linked in: Pid: 0, comm: swapper Tainted: G D W 2.6.28-rc4-dirty #5 Call Trace: [<ffffffff8023af92>] warn_on_slowpath+0x62/0xa0 [<ffffffff803a4159>] vsnprintf+0x449/0x6b0 [<ffffffff803a3a84>] string+0x34/0xf0 [<ffffffff803a4118>] vsnprintf+0x408/0x6b0 [<ffffffff802547dd>] up+0xd/0x40 [<ffffffff8023b6de>] release_console_sem+0x1ae/0x200 [<ffffffff8021ef40>] stop_this_cpu+0x0/0x30 [<ffffffff8025db9e>] smp_call_function_mask+0x1de/0x250 [<ffffffff803a3f78>] vsnprintf+0x268/0x6b0 [<ffffffff80615074>] printk+0x40/0x45 [<ffffffff8021ef30>] native_smp_send_stop+0x20/0x30 [<ffffffff80614f8d>] panic+0x82/0x129 [<ffffffff8023ecae>] do_exit+0x7de/0x890 [<ffffffff80615074>] printk+0x40/0x45 [<ffffffff806184ba>] oops_end+0x7a/0xc0 [<ffffffff8020d3d4>] do_invalid_op+0x84/0xa0 [<ffffffff808d69e7>] xsave_cntxt_init+0x35/0x130 [<ffffffff8023b6de>] release_console_sem+0x1ae/0x200 [<ffffffff802547dd>] up+0xd/0x40 [<ffffffff806178e9>] error_exit+0x0/0x51 [<ffffffff808d69e7>] xsave_cntxt_init+0x35/0x130 [<ffffffff808d69e7>] xsave_cntxt_init+0x35/0x130 [<ffffffff8060e2b1>] fpu_init+0x4a/0x97 [<ffffffff8060fa3f>] cpu_init+0x319/0x33f [<ffffffff808cdab5>] start_kernel+0x1b2/0x321 [<ffffffff808cd405>] x86_64_start_kernel+0xd9/0xdd ---[ end trace 4eaa2a86a8e2da22 ]--- Thanks and best regards, Faisal On Sat, Jul 15, 2017 at 5:32 AM, Gabe Black <[email protected]> wrote: > The x86 interrupt controller architecture gem5 implements is described in > the Intel MultiProcessor Specification which is about 20 years old, and is > a standard called APIC. Looking at the spec, it has an 8 bit ID register > and so up to 255 APICs can have unique IDs. I see on the internet folks > saying the local APICs (ie. the ones attached to each CPU) only have a 4 > bit ID field, so that actually limits you to 15 devices. > > If you want to support more CPUs, you'd probably want to implement a new > standard like xAPIC or x2APIC. xAPIC apparently makes the ID field 8 bits > again which would make it possible to address 255 CPUs. The little bit of > the x2APIC spec I looked at seems to say it supports 32 bit IDs, so enough > that the limit could be considered arbitrarily high, and a logical > destination addressing scheme (ie. a bit vector of target IDs, I believe) > which supports a clustering concept which makes it able to address more > CPUs too. > > Gabe > > On Fri, Jul 14, 2017 at 8:17 AM, <[email protected]> wrote: > >> Thanks for earliest reply. >> >> 1. I know how to set the 256 core in Linux kernel using make menuconfig. >> However, the main problem is the current gem5 version is not even >> allowing to run the 16 core for Linux kernel 2.6.28.4, which is always >> showing kernel panic as I mentioned below. Old version like- 2.7.22.9.smp >> is running fine but I don't have the original package (don't find it in >> kernel.org). So I can't reset the number of core. >> 2. My target is to get exactly 256 core benchmark performance. So, I also >> like to change those files to obtain those results. >> >> Thanks and best regards, >> >> Faisal >> >> On Jul 14, 2017, at 11:32 PM, Jason Lowe-Power <[email protected]> >> wrote: >> >> Hello, >> >> A couple of points: >> 1. You probably will need to compile a custom Linux kernel to support 256 >> cores. This isn't something that is expected to work out of the box. >> 2. I don't think gem5 supports more than 256 cores (and maybe not that >> many) without making code modifications. I believe there are a few places >> where we use a core bitvector, and I doubt it's bigger than 64-bits. >> >> Jason >> >> On Fri, Jul 14, 2017 at 6:03 AM F. A. Faisal <[email protected]> wrote: >> >>> Dear All, >>> >>> I basically want to run the benchmarks like- splash or parsec with 256 >>> cores. >>> >>> Hence, I tried with X86 ISA with the linux kernel from the Parsec site ( >>> http://www.cs.utexas.edu/~parsec_m5/), which returns the kernel panic >>> with "warn: x86 cpuid family 0x0000: unimplemented function 13". >>> >>> And even I downloaded the kernel from (https://www.kernel.org/pub/li >>> nux/kernel/v2.6/) (both .bz2 and .gz), which also returns the kernel >>> panic with the same warning message (kernel BUG at >>> arch/x86/kernel/xsave.c:323). >>> >>> On the other hand, I download the X86 disk image from- >>> >>> - X86 full system image: >>> [http://www.m5sim.org/dist/current/x86/x86-system.tar.bz2]. >>> >>> Then, I also tried "x86_64-vmlinux-2.6.22.9.smp" which is running fine with >>> maximum 8 cores and obviously can't increase the core number. >>> >>> Please let me know download link for the stable Linux kernel of X86. >>> >>> GEM5> (USED GIT Repository, Download- 28/06/2017) >>> >>> Thanks in advance. >>> >>> Best regards, >>> >>> F. A. Faisal >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> gem5-users mailing list >>> [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 list >> [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 list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
