Hi Farbin,
I think that change/fix is already merged.
-Ayaz
On Wed, Apr 12, 2023 at 1:47 PM Farbin Fayza wrote:
> Hi everyone, thank you very much for co-operating. The stat file errors
> were resolved by the change that Humza mentioned. The stat file now
> contains non-zero metrics. Should I
[AMD Official Use Only - General]
Hello,
I don't know how to change the frequency or if it will work, but in your gem5
python script you can call "m5.simulate(10 * 1e12)" to simulate 10 seconds
worth of ticks at a time and change the frequency after each call to that.
-Matt
From: Mejbaul Is
This is what I did and made it work. Of course, I did this after I trace where
they increment the cycles and made the changes make sense to me. I am using
v22, so I would image it works for you. But, as Eliot pointed out, there are
more places you need to check. I would suggest you starting with
On 4/13/2023 6:24 AM, Farbin Fayza via gem5-users wrote:
Hi Heng,
Thanks for your reply. Do you mean something like this? I changed atomic.cc
like this:
void AtomicSimpleCPU::drainResume()
{
assert(!tickEvent.scheduled());
if (switchedOut())
return;
DPRINTF(SimpleCPU, "
Hi Heng,
Thanks for your reply. Do you mean something like this? I changed atomic.cc
like this:
void AtomicSimpleCPU::drainResume()
{
assert(!tickEvent.scheduled());
if (switchedOut())
return;
DPRINTF(SimpleCPU, "Resume\n");
verifyMemoryMode();
assert(!threadContexts.
