The checking of memory values occurs at retirement time as well - Opal
reads memory values through a Simics API call readPhysicalMemory() in
memop.C during instruction execution, and the values are put into the
register file to be verified during retirement.
If a mismatch occurs, Opal gets restarted with the correct processor
state and starts execution at the instruction following the load which
violated SC.
Note that memory consistency violations are counted in the "percent
correct" stat in the Opal stats file.
Luke
On Thu, 8 Sep 2005, arrvindh shriraman wrote:
> If GEMS employs an Alpha consistency model, how does
> it verify it's processor state with SIMICS (which
> enforces SC). Won't there be mismatch ? In all such
> cases does OPAL squash the pipeline and load state
> from SIMICS ?
>
> Thanks
>
> Arrvindh Shriraman
> Conputer Science Department
> University of Rochester
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>
|