[gem5-users] Re: IGbE_e1000 card not connected

Hi Nikos, how old is your gem5 checkout? The change below fixed some aspects of how PCI devices are managed, including one which could cause failures like you're seeing. commit 9be18aa66ddb8db4da043279819d45bc72b7b086 Author: Gabe Black Date: Fri Oct 2 03:00:04 2020 -0700 On Wed, Mar 31, 2021

[gem5-users] Re: m5 utility for ARM64

Hi Jeageun, you should take a look at util/m5/README.md for an explanation of how the m5 utility works and how it should be used in different environments. It looks like it's trying to use the instruction based mechanism to call into gem5, and that won't work in KVM. In KVM, you have to use the

[gem5-users] m5 utility for ARM64

Hi all, I'm trying to use m5 exit on the ARM image using http://dist.gem5.org/dist/current/arm/aarch-system-201901106.tar.bz2. I boot this image using the following instruction ./build/ARM/gem5.opt configs/example/fs.py --kernel /data/gem5_image/vmlinux --disk-image

[gem5-users] RISC-V Full system Linux

Dear gem5 community, As I read in this link https://gem5.googlesource.com/public/gem5/+/refs/heads/stable/RELEASE-NOTES.md gem5 v21.0 release includes RISC-V Full system Linux boot support! May you help me please where can I find the Bootloader (bbl), Linux Kernel, and BusyBox image

[gem5-users] IGbE_e1000 card not connected

Dear gem5 community, I would like to use the IGbE_e1000 card in the latest gem5 version in ARM FS mode. As I can see the card is connected only in VExpress_EMM and VExpress_EMM64. However, I cannot boot correctly the latest gem5 version either in VExpress_EMM or VExpress_EMM64 using the

[gem5-users] Re: Fail to Boot Multicore Arm System with KVM CPU

Hi Giacomo, Thanks for your reply. I tried the solution you suggested, but seems there are still problems. Just make sure I understood correctly, I specified the 'machine-type' as 'VExpress_GEM5_V1' and in the VExpress_GEM5_V1_Base class's definition (src/dev/arm/RealView.py), when

[gem5-users] understanding commMonitor output

Hello, I intend to observe all the physical DRAM addresses that are accessed when an application is being executed in full-system mode. Following some earlier discussions on this mailing list, I used the commMonitor. I added the following lines to fs.py file: test_sys.monitor = CommMonitor()

[gem5-users] Re: Fail to Boot Multicore Arm System with KVM CPU

Hi Wenqi, First of all thanks for the detailed explanation of your problem. > -Original Message- > From: wqyin--- via gem5-users > Sent: 30 March 2021 22:47 > To: gem5-users@gem5.org; wq...@utexas.edu > Cc: wq...@utexas.edu > Subject: [gem5-users] Fail to Boot Multicore Arm System with

[gem5-users] Re: KVM usage: x86 host, arm target

Hi Pedro, > -Original Message- > From: Pedro Becker via gem5-users > Sent: 31 March 2021 13:03 > To: gem5-users@gem5.org > Cc: Pedro Becker > Subject: [gem5-users] KVM usage: x86 host, arm target > > Hi all, > > I'm running gem5 (v20.1.0.4) on an x86 machine, targeting an ARM (aarch64)

[gem5-users] KVM usage: x86 host, arm target

Hi all, I'm running gem5 (v20.1.0.4) on an x86 machine, targeting an ARM (aarch64) FS, and I'd like to speed up my simulation (it takes 3 days to finish with AtomicSimpleCPU and I'm still running a 'small' workload, likely to increase a lot). One option I'd like to try is to fast-forward the

[gem5-users] Re: ISSUES FACING WHILE INTEGRATING GEM5 AND DRAMSIM3

Hello, I’m having the same issue with the address range intersection when I use any dramsim3 config file Sent from Mail for Windows 10 ___ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org