MaxTick is unsigned these days so I would think it's 2^64 – 1.
From: Steve Reinhardt <ste...@gmail.com<mailto:ste...@gmail.com>>
Reply-To: gem5 users mailing list
<gem5-users@gem5.org<mailto:gem5-users@gem5.org>>
Date: Tuesday, 9 July 2013 16:16
To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>>
Subject: Re: [gem5-users] Problems with extreme large tick numbers
Really large values like that tend to mean that your simulation is deadlocked,
so few or no events get scheduled. There is a termination event scheduled at
MaxTick to prevent the event queue from wrapping around to zero; that's 2^63-1,
or 9223372036854775807. If you're actually seeing an event at
9223372556892048807, which is 0x8000007914A30DA7, then something is really
weird because you're past MaxTick.
Steve
On Mon, Jul 8, 2013 at 4:06 PM, Dali Zhao
<daviz...@gmail.com<mailto:daviz...@gmail.com>> wrote:
Dear Gem5 community,
I'm using gem5 to do some architecture simulation. I have modified the original
gem5 code. I recently ran into the problem of abnormal tick numbers. The
simulation will stop after 30-40 minutes, due to a large tick number. (The
number I got is 9223372556892048807).
I don't know if anyone has seen it before?
--
Dali Zhao
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org<mailto:gem5-users@gem5.org>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
-- IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
