mem: Cycles converted to Ticks in atomic cache accesses
This patch fixes an outstanding issue in the cache timing calculations where an atomic access returned a time in Cycles, but the port forwarded it on as if it was in Ticks. A separate patch will update the regression stats.
This commit is contained in:
10
src/mem/cache/cache.hh
vendored
10
src/mem/cache/cache.hh
vendored
@@ -263,17 +263,17 @@ class Cache : public BaseCache
|
||||
/**
|
||||
* Performs the access specified by the request.
|
||||
* @param pkt The request to perform.
|
||||
* @return The number of cycles required for the access.
|
||||
* @return The number of ticks required for the access.
|
||||
*/
|
||||
Cycles recvAtomic(PacketPtr pkt);
|
||||
Tick recvAtomic(PacketPtr pkt);
|
||||
|
||||
/**
|
||||
* Snoop for the provided request in the cache and return the estimated
|
||||
* time of completion.
|
||||
* time taken.
|
||||
* @param pkt The memory request to snoop
|
||||
* @return The number of cycles required for the snoop.
|
||||
* @return The number of ticks required for the snoop.
|
||||
*/
|
||||
Cycles recvAtomicSnoop(PacketPtr pkt);
|
||||
Tick recvAtomicSnoop(PacketPtr pkt);
|
||||
|
||||
/**
|
||||
* Performs the access specified by the request.
|
||||
|
||||
Reference in New Issue
Block a user