Hi all

I'm trying to boot arm FS with KVM in an ARM machine (an Nvidia Jetson) with 
multiple cores.
I had it working last year, on gem5 version 21.1.0.0. Later I had to update 
gem5 to version 21.1.0.2 because of some
errors in the stats generation of version 21.1.0.0.

So I had a lot of problems in the way, which were discussed here 
(https://lists.gem5.org/archives/list/gem5-users@gem5.org/thread/VCI74JOSRCQK3N64QRRGV3HLNVEYH4OC/#VCI74JOSRCQK3N64QRRGV3HLNVEYH4OC).
 But it was working.

Now I'm back on using that setup, but I'm getting a weird behavior using the 
fs_bigLITTLE.py script:

Basically, the boot is inconsistent with 8 CPUs. Sometimes it boots, sometimes 
it gets stuck at
[    0.194001] smp: Bringing up secondary CPUs ...

I'm varying the numbers of <BIG_CPUS> and <LITTLE_CPUS> (such that 
<BIG_CPUS>+<LITTLE_CPUS> <= 8) in the command below:

./build/ARM/gem5.opt configs/example/arm/fs_bigLITTLE.py --kernel 
/scratch/pedro/aarch-my-system/binaries/vmlinux.arm64 --disk 
/scratch/pedro/ubuntu-18.04-arm64-8gb.img --cpu-type kvm --kvm-userspace-gic 
--mem-size 8GB --big-cpus <BIG_CPUS> --little-cpus <LITTLE_CPUS> --bootscript 
configs/boot/hello.rcS

Using 8 big CPUs generally cause it to get stuck, actually. Using 7 or fewer 
CPUs never made caused it to get stuck. Big little configurations seem to boot 
fine (e.g. 6 big + 2 little).
I wonder if it is because of using a simulated GIC to provide support to 8 CPUs.

Is that a known behavior?
Any workaround?

Thank you.
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to