d on the MESI protocol (inclusive cache
> hierarchy), a block in L1 cache should also be in the L2. Is it correct?
> Thanks for your help.
>
>
> Best,
> Yingying
>
>
>
> Date: Tue, 16 Oct 2012 18:09:16 -0400
> From: Malek Musleh
> To: gem5 users mailing list
cache should also be in the L2. Is it correct?
Thanks for your help.
Best,
Yingying
Date: Tue, 16 Oct 2012 18:09:16 -0400
From: Malek Musleh
To: gem5 users mailing list
Subject: Re: [gem5-users] Questions about DataBlock in Ruby
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
Hi Yingying,
NetDest indicates in which of the Memory Caches the address is present
in the protocols MachineType. In the case for MESI there are 4:
(L1Cache, L2Cache, Directory, DMA).
[NetDest (4) 0 1 - 0 0 - 0 - 0 - ]
In this case the tag is present only in the second L1Cache (L1Cache1)
[N
Hi,
I am sorry but I was wrong for the 1st question. When I run the simulator
long enough it started printing out data blocks with real value. So I think
the all-zero information is not the real simulation.
But I still have the 2nd question. When I set my system as 2-core CMP,
MESI_CMP_directory
Hi,
I have a question about the data fetched from main memory. As in
MESI_CMP_directory-L2cache.sm, action "ee_sendDataToGetXRequestor' sends
the cache block (phyaddr and real data) to the requestor. It also prints
out the debug information as " DPRINTF(RubySlicc, "Address: %s,
Destination: %s, Da
