Re: [Gems-users] question on time in eventqueue

["Lei Yang" <lya755@xxxxxxxxxxxxxxxxxxxx>]

Thanks Mike! I guess I'll change the delay to 1 instead of removing the many 
'asserts'. I've tried to remove some, but the result is just more other 
errors :-(
One other question is (may seem unrelated, sorry),  is there an easy way in 
ruby to find out the instruction count of one processor?
TIA!

Lei
----- Original Message ----- 
From: "Mike Marty" <mikem@xxxxxxxxxxx>
To: "Gems Users" <gems-users@xxxxxxxxxxx>
Cc: "Lei Yang" <lya755@xxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, January 25, 2007 9:54 PM
Subject: Re: [Gems-users] question on time in eventqueue


> > SLICC defines a state machine -- no state can change more than once per 
> > cycle, so all future transitions,
> > output changes, etc, must have at least delay 1.
> Thats not really true.  A state can change more than once in a cycle.
> For example, a Directory controller could receive two GETS messages in the
> same cycle that are both handled (and both potentially state changing..for
> example the first GETS could transition to S where the second might
> transition to SS indicating multiple outstanding GETS requests).
>
> The EventQueue is a priority heap.  Adding a new entry that is the minimum
> could be dicey...for example if could change the current root of the tree.
> We've always enforced that adding something to the EventQueue must have a
> wakeup at least 1 cycle in the future.  If you try modifying this
> behavior, I'd be interested to hear your experiences.