[gem5-users] Re: some problem about IO device's write or read function's return tick

2021-12-27 Thread Gabe Black via gem5-users
I think this may not be quite right, or I'm misunderstanding what Jason is saying. The Tick number returned in atomic mode is supposed to approximate how long the access took, and it's up to the caller to do something with that. Often the caller does throw away the number, but that's what it's

[gem5-users] Re: some problem about IO device's write or read function's return tick

2021-12-27 Thread Jason Lowe-Power via gem5-users
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