After 2 hours, message appear in m5term. My CPU is xeon e5 2687w v3, I think the boot time is too long, are there any way to accelerate it?
---Original---
From: "Jason Lowe-Power via gem5-users"<gem5-users@gem5.org>
Date: Wed, Aug 23, 2023 23:13 PM
To: "The gem5 Users mailing list"<gem5-users@gem5.org>;
Cc: "oe-fans"<55839476@qq.com>;"Jason Lowe-Power"<jason@lowepower.com>;
Subject: [gem5-users] Re: can't run riscv simulation with any CPU model except Atomic
Hello,
These scripts are tested nightly, so they should be working. How long did you wait for the terminal output? It can take 15-30 minutes before you see any output.
Cheers,
Jason
On Wed, Aug 23, 2023 at 5:00 AM oe-fans via gem5-users <gem5-users@gem5.org> wrote:
hi, all
I built gem5 v23.0.1.0, I can run configs/example/lupv/run_lupv.py with atomic CPU model successful. But when I run it with TIMING model, there is nothing appear in m5term.
I try configs/example/gem5_library/riscv-fs.py or riscvmatched-fs.py, neither of them can boot.
What's wrong with my gem5 build? Are there anything I missing?
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.org
On 8/24/2023 1:35 AM, oe-fans via gem5-users wrote:
After 2 hours, message appear in m5term. My CPU is xeon e5 2687w v3, I think the boot time is too
long, are there any way to accelerate it?
I have seen it take longer if the number of cpus told to gem5
does not match the number of cpus in the Linux dtb file. This
was a while ago, so I'm not sure it's still true ...
Best - Eliot Moss
If you are referring to the RISC-V Full System simulations. Yes, they are very slow. 2 hours seems normal to me. I've seen them take longer.
--
Dr. Bobby R. Bruce
Room 3050,
Kemper Hall, UC Davis
Davis,
CA, 95616
On Aug 24, 2023, at 5:23 AM, Eliot Moss via gem5-users gem5-users@gem5.org wrote:
On 8/24/2023 1:35 AM, oe-fans via gem5-users wrote:
After 2 hours, message appear in m5term. My CPU is xeon e5 2687w v3, I think the boot time is too long, are there any way to accelerate it?
I have seen it take longer if the number of cpus told to gem5
does not match the number of cpus in the Linux dtb file. This
was a while ago, so I'm not sure it's still true ...
Best - Eliot Moss
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.org