Hello, If you are using *atomic* memory mode, then the tick number is mostly ignored. If you're using *timing* mode, then the tick number should be used by whatever object calls the read/write function and the delay is inserted there. Also, if your program doesn't have a direct dependence on the I/O device, the latency may be hidden. Enabling various debug flags should help you track this down.
Cheers, Jason On Thu, Dec 23, 2021 at 8:58 AM lin via gem5-users <gem5-users@gem5.org> wrote: > Hi > > I make an IO device link to the membus and complete the Tick > read(PacketPtr pkt) and the write() function .But I find that no matter how > many ticks ( the funciton return n*tick) I set,the simSeconds no change.If > it normal?If not , what can I do to set the return ticks of the read() or > write() function? > > Thanks everyone! > > > > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
