Hi Boyang,
dist-gem5 defines a unique hostname for each simulated system as a convenience
for the user. It is not obligatory, you can use IP addresses directly instead
of hostnames. dist-gem5 does not require DNS.
- Gabor
From: gem5-users on behalf of Boyang Xu
<6172...@gmail.com>
Reply-To:
Hi, All
I think I found the root cause of this issue, I define a timing cpu model in
the createCPU(), and missing the createThreads() call
My code is below:
def createCPU(self):
self.cpu = [AtomicSimpleCPU(cpu_id = i, switched_out = False)
for i in ran
Hi Jimmy,
Oops. I thought I sent this yesterday... sorry :). It looks like you
figured it out in the meantime.
That branch is a little old. You also need to call createThreads() on the
timingCpus. See
https://github.com/darchr/gem5/blob/feature/simplefs/configs/myconfigs/system/system.py#L140
cr
Thanks for the suggestions.
I have been trying a couple of solutions (I only test for a small subset
of decapo benchmark suite, which encounters segfault with O3CPU):
1. using TimingSimpleCPU: no segfaults
2. disable COW layer and write on the disk image when taking checkpoint:
there are still se
JIT was precisely the issue I was thinking was causing this. One thing may be
necessary, that is to ensure you sync the disk image before taking your
checkpoint.
gem5’s debug flags should help you identify something like a hang, for example
an ExecAll trace. A SyscallAll trace would most likely
Hey Gutierrez,
"*sync* the disk image", do you mean making sure all disk modifications are
actually made on the disk (update to date) before taking the checkpoint?
How to do that?
I haven't tried to take a checkpoint with COW layer disabled and then
restart from that checkpoint before. All I have
Yes, make sure all buffers are flushed, etc., before taking your checkpoint you
can call the “sync” command, which should be already installed on the image.
You’ll need to call sync before your commands to halt and take a checkpoint.
This page explains how I did the same for an Android disk imag
Thanks a lot for the tips. I will give a try.
best,
Da
On Thu, Jul 19, 2018 at 3:12 PM Gutierrez, Anthony <
anthony.gutier...@amd.com> wrote:
> Yes, make sure all buffers are flushed, etc., before taking your
> checkpoint you can call the “sync” command, which should be already
> installed on th
I just did a quick test for one benchmark using sync and no COW layer, but
it still encountered SIGSEGV. I took the checkpoint by running the
benchmark in the background as root (with KVM CPU); I warmed up JIT for 1
round and took the checkpoint in the second round by using "sync && m5
exit" with -
