Hi Arthur, Thanks a lot for your response. It makes sense that nothing happens to the cache on a syscall (no writebacks, etc.) since it is physically indexed and physically tagged. That is what I was wondering in the first place.
-Murat. From: Arthur Perais Sent: Thursday, May 26, 2016 4:29 PM To: gem5 users mailing list Subject: Re: [gem5-users] Cache properties Hi Murat, 1) As far as I am aware, only PIPT caches are implemented in gem5 (arguably the L1 can be VIPT as a result of using the correct combination of associativity/number of sets and page size). If you want a virtual cache, you'll have to implement it yourself, and this is not going to be trivial if you want coherence to work, I reckon. 2) Nothing particular, I would say. Arthur. De: "Murat Koksal" <[email protected]> À: [email protected] Envoyé: Jeudi 26 Mai 2016 22:20:27 Objet: [gem5-users] Cache properties Hello, I am trying to find certain information about the caches employed in se.py. I am aware that some configuration options are available in gem5/configs/common/Caches.py file, but so far I haven't found what I am looking for. I was wondering if anybody could direct me in the right direction. What I would like to know is 1) where is it specified that a cache uses physical/virtual addresses for indices/tags, and 2) what happens to the cache contents upon a syscall? Thanks. _______________________________________________ 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
