Thanks for your help. I found it. ☺
2013/2/5 Tao Zhang
> **
> Hi Yinchong,
>
> I am not quite sure the exact meaning of "memory initialization" you
> mentioned (DRAM initialization steps? or Data initialization). If you care
> about how data is accessed by the gem5, I may give you some clue.
>
Hi Ali,
That's what I'm looking for. Thank you very much.
Regards,
Yinchong
2013/2/6 Ali Saidi
> **
>
> Before the cpu starts executing the code in src/base/loader/* loads the
> binary into memory (the instructions) and the code in
> src/arch/**/process.cc builds up a stack frame as appropria
Before the cpu starts executing the code in src/base/loader/* loads
the binary into memory (the instructions) and the code in
src/arch/**/process.cc builds up a stack frame as appropriate for the
architecture/OS that you're simulating.
Ali
On 05.02.2013 18:22, Tao
Zhang wrote:
> Hi Yinchon
Hi Yinchong,
I am not quite sure the exact meaning of "memory initialization" you
mentioned (DRAM initialization steps? or Data initialization). If you
care about how data is accessed by the gem5, I may give you some clue.
In SE mode, your host machine first allocates a large memory space for
you
I think that it's Main Memory.
It shows like below：
0: 0: system.physmem: Write of size 4096 on address 0x0
0: system.physmem: 7f 45 4c 46 01 01 01 00 00 00 00 00 00
00 00 00ELF
0: system.physmem: 0010 02 00 28 00 01 00 00 00 34 9c 00 00 34
00 00 00 (
do you mean cache or main memory?
-Tao
On 02/05/2013 11:46 AM, Yinchong Feng wrote:
Hi All,
I'm new at using gem5, and I'm trying to run benchmarks on gem5 in SE
mode. I feel confused about the momory initialization in SE mode. When
I ran the bianries with debug-flags MemoryAccess, MemDepUni
Hi All,
I'm new at using gem5, and I'm trying to run benchmarks on gem5 in SE mode.
I feel confused about the momory initialization in SE mode. When I ran the
bianries with debug-flags MemoryAccess, MemDepUnit and MemTest, I saw that
the memory was initialized before the real simulation starting.
