Thanks.
Does it mean that even you stall a memory transaction with stall time
200000000000
It will come to timing-model again next cycle, anyway?
在2008-04-04,"Dan Gibson" <degibson@xxxxxxxx> 写道:
Often, a memory stall time is not known at request-time. In this
case, Ruby stalls Simics for a long long long time, but un-stalls
it when Ruby determines its coherence actions have been completed.
Regards,
Dan
pathscale wrote:
Hi,
I'm studying ruby's core and I'm curious about how a memory
transaction can be returned with stall time like this:
{ Miss , SIMICS_STALL_TIME},
which is to say an infinite stall time.
I don't know in what condition this is supposed to happen.
Thanks
------------------------------------------------------------------------
中国 最 强 网 游 --- 网 易 梦幻 西 游 ,166 万 玩 家 同 时 在 线
<http://event.mail.163.com/chanel/click.htm?from=NO_26&domain=126>
------------------------------------------------------------------------
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.
--
http://www.cs.wisc.edu/~gibson [esc]:wq!
------------------------------------------------------------------------
中国 最 强 网 游 --- 网 易 梦 幻 西 游 ,166 万 玩 家 同 时 在 线
<http://event.mail.163.com/chanel/click.htm?from=NO_26&domain=126>
------------------------------------------------------------------------
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.