Hello List,
I am using the monitor/listener utilities of gem5's system call simulation. I
am working on x86 binaries. I have set the memory space as 4G in the
configuration file. I set a monitor/listener between the CPU and the L1DCache.
Currently, I found it is hard to interpret the recorded memory address in the
dumped trace.
Suppose I am monitoring the following memory access:
movzbl 0x81aa1a0(%edx),%eax
Since the base address of the above load operation is 0x81aa1a0, I expect that
the recorded memory address in the trace should be larger or at least equal to
0x81aa1a0. However, all the recorded memory address is something like:
r,1450420,1,3,5178814000
r,1450404,1,3,5180762000
r,1450403,1,3,5182652000
r,1450401,1,3,5186636000
.....
As you can see, the recorded memory address (1450420; 1450404..) is quite
small..
Another observation is that, when the offset of the above memory access
changes, the recorded memory address would not change. I have did some
experiments, by changing the register "edx" into different values. However, I
have confirmed that the recorded memory address sequence during runtime stays
the same.
It seems that something obviously went wrong here... But I really have no idea
what happened. Am I missed anything here?Any suggestion or advice would be
appreciated. Thank you.
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
