[gem5-users] Re: What happens when a atomic only port is accessed in Timing simulation?

Hi Zehan, I wouldn't say it converts the timing request to atomic. Instead, I would say that for the *functional access* (sorry for the overloaded term here... I mean functional as in the place it does the "execution" part of the model) it uses the same C++ function for both timing and atomic.

[gem5-users] Re: What happens when a atomic only port is accessed in Timing simulation?

Thanks for your advice. My guess is that it's the ports connected to the atomic-only port converts a timing request to atomic, and calls the recvAtomic function. In this case it's the XBar. I will try to measure how it's delayed. From: Jason Lowe-Power Sent:

[gem5-users] Re: What happens when a atomic only port is accessed in Timing simulation?

Hi Zehan, Atomic memory accesses should not be used during the same simulation loop as timing accesses. I.e., you should not call "sendAtomic" on a port during the same simulation loop that you call "sendTiming". If there isn't a panic in that case, there probably should be. If you want to get a