Hi Amirali,

Just to be clear, the MinorCPU supports multicore just fine. We even use it for 
heterogeneous multi-core configs (big and little cores). You may want to try a 
more recent kernel. For ARM, anything up till 4.3 works. There are instructions 
on the wiki for how to build a more recent kernel 
(http://www.gem5.org/ARM_Linux_Kernel).

I hope that helps.

Andreas

From: gem5-users 
<[email protected]<mailto:[email protected]>> on behalf of 
Amirali Boroumand 
<[email protected]<mailto:[email protected]>>
Reply-To: gem5 users mailing list 
<[email protected]<mailto:[email protected]>>
Date: Thursday, 8 October 2015 at 22:43
To: gem5 users mailing list <[email protected]<mailto:[email protected]>>
Subject: Re: [gem5-users] Minor CPU in X86

I solved the issue. The MinorCPU should be added to CPU_MODELS in the 
build_opts/X86. Now the problem is that the simulation crashes when I run 
multicores. Seems like MinorCPU doesn't support multicore. It keeps generating 
following error:


 command line: build/X86/gem5.opt --debug-flags=MinorCPU -d result2/ 
configs/example/fs.py --cpu-type=minor --num-cpus=2 
--kernel=/home/amirali/gem5/binaries/x86_64-vmlinux-2.6.32-smp 
--disk-image=/home/amirali/gem5/disks/linux_x86_16GB_2 --caches --ruby

Global frequency set at 1000000000000 ticks per second

warn: DRAM device capacity (8192 Mbytes) does not match the address range 
assigned (512 Mbytes)

info: kernel located at: /home/amirali/gem5/binaries/x86_64-vmlinux-2.6.32-smp

Listening for com_1 connection on port 3456

      0: rtc: Real-time clock set to Sun Jan  1 00:00:00 2012

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

warn: Reading current count from inactive timer.

      0: system.cpu0: ActivateContext thread: 0      0: system.cpu1: 
SuspendContext 0

**** REAL SIMULATION ****

      0: system.cpu0: MinorCPU startup

      0: system.cpu0: ActivateContext thread: 0      0: system.cpu1: MinorCPU 
startup

      0: system.cpu1: ActivateContext thread: 0      0: system.cpu1: 
ActivateContext thread: 0info: Entering event queue @ 0.  Starting simulation...

panic: invalid access size(?) for PCI configspace!

 @ tick 83500

[read:build/X86/dev/pciconfigall.cc, line 72]

Memory Usage: 814808 KBytes

Program aborted at cycle 83500


Any help would be appreciated!

On Thu, Oct 8, 2015 at 4:00 PM, Amirali Boroumand 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

I'd like to use Minor CPU type for X86 system, but it seems that it is only 
supported in ARM and Alpha. Is there anyway I could use Minor CPU type for X86 
System?

Thanks!

Best,
Amirali

--
--
Amirali Boroumand
PhD Student
Carnegie Mellon University



--
--
Amirali Boroumand
PhD Student
Carnegie Mellon University

________________________________

-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to