Memory Trace

Each instruction fetch will generate two memory references:
one to the page table to find the physical frame that the instruction resides
within, and one to the instruction itself to fetch it to the CPU for processing.
In addition, there is one explicit memory reference in the form of
the mov instruction; this adds another page table access first (to translate
the array virtual address to the correct physical one) and then the array
access itself.

>>> 40000>> 10
39
>>> 7*1024
7168
>>> 7*1024 + (40000 & 0b1111111111)
7232
>>>

See if you can make sense of the patterns that show up in this visu-
alization. In particular, what will change as the loop continues to run
beyond these first five iterations? Which new memory locations will be
accessed? Can you figure it out?