Thanks for the detailed emails Lisa and Brad.
The commentary is very MUCH appreciated and I'm just currently looking
through code and figuring out how I want to get "my stats" out of the
MOESI_CMP_directory protocol.
I guess adding your own stats are easy but validating them is a little
bit trick
I don't have anything definitive about Ruby vs. M5 stats, but until there is
anything definitive, I use both depending on what I'm trying to do.
I've added my own M5 stats to the Ruby Caches because I know those stats
much better, but I've also looked at existing Ruby stats when I know they
answer
> > I realize the documentation is still under way for gem5, but I was
> > wondering if there are any plans to document how users should be
> > interpreting the Ruby stats file? (Particularly, the miss latency
> > histograms)
Not all protocols support the miss latency histograms. Specifically,
Hi,
not to push and prod, but if anyone has any ideas or thoughts on this,
please speak up!
Thanks!
-Korey
On Tue, Apr 5, 2011 at 12:54 PM, Korey Sewell wrote:
> Hi All,
> I realize the documentation is still under way for gem5, but I was wondering
> if there are any plans to document how users
Hi All,
I realize the documentation is still under way for gem5, but I was wondering
if there are any plans to document how users should be interpreting the
Ruby stats file? (Particularly, the miss latency histograms)
Did people come to the conclusion that it is a good idea to have a separate
fil
