Thanks a lot.
On Mon, Oct 28, 2013 at 9:36 AM, Ali Saidi <[email protected]> wrote: > ** > > The value is written to the cache which notices it's non-cacheable and > passes it to the next level of the memory system. This continues until the > request reaches the memory it's destined for. > > > > Ali > > > > On 23.10.2013 15:27, Xiangyang Guo wrote: > > Hi, > > can anyone tell me how gem5 handles the uncacheable write? For example. > maybe there is an inst which is a memory write, but this write is to change > the frame buffer value, then this request should be uncacheable? Am I right > here? In this case, how gem5 handles it? Does this request go to cache? In > cache_impl.cc the function access(), if it is uncacheable, we just flush > it. But we will use this value of the memory write no matter what, because > we need this value to change the LCD. So could any one tell me what's going > on? Where should we store this data? Thanks a lot. > > regards > > Xiangyang > > _______________________________________________ > gem5-users mailing > [email protected]http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > > > > > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
