Hi Giacomo,
Thanks for your reply. According to your guidance, I have solved my problem!
Best Wishes,
Chao
-- Original --
From:
"gem5 users
Ciro,
When I merged the changes in from that patch and its relations I started
getting a crash instead of a hang. That crash, I can reproduce on develop.
gem5.opt: build/X86/cpu/o3/cpu.cc:823: void
FullO3CPU::removeThread(ThreadID)
[with Impl = O3CPUImpl; ThreadID = short int]: Assertion
`commit.
Yes, I had also previously observed that debug symbols make the huge majority
of the executable's size, and for some reason much more so in .opt than in
debug (presumably it takes more information to map back optimized code to
source).
You can confirm that by using strip gem5.opt or gcc- s duri
Daniel, if you manage to reproduce on clean develop, please also open an issue
at https://gem5.atlassian.net/jira/software/c/projects/GEM5/issues I'd also be
curious to see if it reproduces on se.py (so I could see if it also happens on
ARM).
We've had some ARM-specific SE issues e.g. at
https
BTW I pushed a patch exposing m5_exit_addr at:
https://gem5-review.googlesource.com/c/public/gem5/+/36896
And after that this should work on KVM
https://gem5-review.googlesource.com/c/public/gem5-resources/+/36677/1
From: Gabe Black via gem5-users
Sent: Wednesda
Hi,
>From the command line you posted I can see you are using the following DTB
>binary:
--dtb-file=./system/arm/dt/armv8_gem5_v1_1cpu.dtb
This is informing the Linux kernel there is one cpu only
(armv8_gem5_v1_1cpu.dtb). That's why you don't see the other ones.
You should change DTB binary or
