On 1/30/2023 7:08 AM, Ivica B wrote:
Can you please share the instructions on how to do it?
On Sun, Jan 29, 2023, 9:07 PM Eliot Moss <m...@cs.umass.edu
<mailto:m...@cs.umass.edu>> wrote:
I have used lackey to get traces, which I have fed into
a cache model to detect conflicts and such. You could
also start with the lackey code and model the cache model
into the tool (which a student of mine did at one point).
Lackey is one of the built-in valgrind tools. It has instructions.
It produces a trace giving one memory access per line, and indicating
if the access is for instruction fetch, memory read, memory write, or
both read and write, with the address and size.
You write a program to parse that and run your own model of whatever
cache you're concerned with. Doing that part is for you to figure
out. You do need to know the details of the cache you're going to
model. There may be programs or libraries out there for analyzing
address traces, but this would not be the list to find them.
Sorry, but I'm not prepared to go through how to code a cache model ...
EM
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
