|
From: Milind <km...@gm...> - 2010-01-11 05:02:40
|
Hi, Is there anyone who has explored interfacing Valgrind output to DRAMsim ? With --trace-mem option, I can see valgrind generates information about memory access type (load, store, modify etc), the address at which the operation was done and the size of the memory access. DRAMsim needs information about every memory access in terms of the address at which the operation took place (this valgrind provides), the operation type (valgrind gives it but there is difference between valgrind output and DRAMsim input) and the cpu tick when the operation was requested. I have following general queries about valgrind - does the output of --trace-mem take take into account the cache accesses? i.e. if the request if going to be fulfilled by cache, there is no 'real' memory operation per se. Or --trace-mem gives all the operations independent of whether it hits the cache or not - how do I get the value of cpu tick at which the operation took place ? - I can write a program to take valgrind --trace-mem output file and generate input file needed by DRAMsim unless there is any easy way to twick valgrind the generate output that I need. Any pointers in the valgrind code will help for this, if any Thanks, - Milind |