Hi Jorge, and thanks for your answer.
Actually I don't understand how this random memory delay could be
related to the tester, as it seems to be related to usual ruby operation.
Marco
Jorge Albericio ha scritto:
The random delay is inserted at memoryResponseLatency (RubyConfig.h)
regards,
2008/10/1 Marco Solinas <marco.solinas@xxxxxxxxxxxx>:
Hi list,
when I use the "random tester" (GEMS 1.4) to debug my protocol, I see
message interleaving even if the physical NoC architecture
(FILE_SPECIFIED) wouldn't allow such kind of race.
Reading the PowerPoint slides (isca_tutorial) available in the website,
I can read that the tester "randomly inserts delay".
My question is: where is this delay inserted? I was wandering that the
strange phenomenon I can see while testing could be tiled to such delay
(I mean: a random delay in the time a queued message is served might
explain such situation).
In the case I'm right, could you suggest me the point in the tester or
ruby code I have to modify in order to avoid such situation?
Thanks a lot!
Marco
_______________________________________________
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.
|