Hi Jinchun, None of the ruby protocols correctly calculate cache hits/misses. They basically call uu_profileMiss Action which just samples the type of Cache Request it is. I have a posted a patch on the review board some time ago that calculates them for MOESI_CMP_directory and MESI. You can do something similar for the hammer protocol.
http://reviews.gem5.org/r/1467/ Malek On Sat, Dec 8, 2012 at 9:38 AM, Jinchun Kim <[email protected]> wrote: > I'm using MOESI_hammer. > > Jinchun Kim > > On Dec 8, 2012, at 4:02 AM, Nilay Vaish <[email protected]> wrote: > >> On Fri, 7 Dec 2012, Jinchun Kim wrote: >> >>> Hi, All. >>> I was wondering if anyone can make a quick check for L2cache misses in ruby. >>> It seems like the number of L2cache access and miss doesn't show proper >>> numbers. >>> In my simulation, L2cache miss is the exactly same number of L1Dcache miss >>> + L2Icache miss... >>> For example... >>> >>> L1 Dcache Access 110,727,153 >>> L1 Dcache Miss 16,211,471 >>> L1 Icache Access 160,428,716 >>> L1 Icache Miss 11,606 >>> L2 Cache Access 271,155,869 >>> L2 Cache Miss 16,223,077 >>> >>> This doesn't make sense because L1Dcache miss+ L2Icache miss should be the >>> number of access to L2cache. >>> I don't understand why ruby collect L2 cache access and miss in this way.. >>> Is there any way to calculate ACTUAL L2 cache access and misses? >> >> Which protocol are you using? >> >> -- >> Nilay > _______________________________________________ > 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
