Hi mehmet,

I have posted a patch on the review board that does this:

http://reviews.gem5.org/r/1467/diff/

If I recall, I only apply it to the MOESI_CMP, MESI protocols. You can
take a look, or apply the diff (not sure if it will apply cleanly on
the dev repo).

Malek

On Fri, Feb 15, 2013 at 9:26 AM, mehmet basaran
<[email protected]> wrote:
> Hi all,
>
> I am trying to get the cache miss & hit ratio counts. I started in se mode,
> and observed that by using normal caches in config files, I always get
> miss_rate="1"
>
> So I decided to use ruby_fs mode instead. But ruby.stats file doesn't give
> me a miss ratio or hit count.  It seems to me that I cannot get miss & hit
> counts correct whether I use ruby or not. Is this the case? Does gem5 has
> built in mechanism for getting cache miss&hit rates? (without modifying the
> code)
>
> In addition I have couple of concepts I need to know in ruby.stats file;
> 1. All Non-Zero Cycle Demand Cache Accesses
> 2. ruby_cycles_executed: [ 10904501813 ]
> 3. "miss_latency_Locked_RMW_Write_L1Cache: [binsize: 1 max: 3 count: 1374
> average:     3 | standard deviation: 0 | 0 0 0 1374 ]"
> what is binsize here ?
>
> Do we have any documentation about the content of ruby.stats file?
>
> My commands;
>
> For se:
> ./build/X86/gem5.opt --debug-flags=Cache --trace-file=my_trace.out
> configs/example/se.py --caches --l2cache --cpu-type=timing -c
> tests/test-progs/queens/bin/x86/linux/queens --options="-c 8"
>
> For fs:
> ./build/X86/gem5.fast configs/example/ruby_fs.py --num-cpus="8"
> --kernel="x86_64-vmlinux-2.6.22.9" --l1i_size="32kB" --l1d_size="32kB"
> --l2_size="8MB" --num-l2caches="8" --topology="Crossbar" --cpu-type="timing"
> --script="boot/my_script.rcS"
>
> Thanks in advance.
>
> _______________________________________________
> 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

Reply via email to