CMU-SAFARI/ramulator

Does it take care of Cache simulation on the memory trace?

Opened this issue · 0 comments

I'm providing it with a memory trace generated using the Intel PIN tool, which simply registers all the read/write requests to the trace file. I wanted to know whether the cache simulation part (cache hits/replacement, etc. ) is taken care of implicitly by ramulator, or do we have to create the cache logic on our own?