Reading the code, it seems to me that one can never checkpoint the state
of an atomic CPU while an atomic operation is going on. Here is some code
for help --
AtomicCPU::tick()
{
for (int i = 0; i width || locked; ++i) {
// break if cpu in idle state
Hey guys,
I've tried searching around, but I'm having trouble finding any help on
this. Anyone have insights or pointers? Is checkpoint restore supposed to
be working?
---
joel@vein:~/research/gem5/gem5-latest$ ./build/X86/gem5.debug
Joel, you might know that system being restored from a check point starts
with an atomic cpu by default. I think the problem you are facing is in
initializing a timing CPU. IIRC, the interrupt controller is moved from
atomic CPU to timing CPU after X number of ticks. You might want to try
Developer List
Subject: Re: [gem5-dev] x86 Checkpoint Restore Trouble
Joel, you might know that system being restored from a check point starts with
an atomic cpu by default. I think the problem you are facing is in
initializing a
timing CPU. IIRC, the interrupt controller is moved from atomic CPU
-
From: gem5-dev-boun...@gem5.org [mailto:gem5-dev-boun...@gem5.org]
On Behalf Of Nilay Vaish
Sent: Tuesday, April 03, 2012 6:51 PM
To: gem5 Developer List
Subject: Re: [gem5-dev] x86 Checkpoint Restore Trouble
Joel, you might know that system being restored from a check point starts with
an atomic
multiple experiments
using the timing cpu.
Brad
-Original Message-
From: gem5-dev-boun...@gem5.org [mailto:gem5-dev-boun...@gem5.org]
On Behalf Of Nilay Vaish
Sent: Tuesday, April 03, 2012 6:51 PM
To: gem5 Developer List
Subject: Re: [gem5-dev] x86 Checkpoint Restore Trouble
