As long as you agree that we should move further on this, I can assure
that I'll write a script that will post process the statistics so that one
can have statistics for the ruby part in a format similar to the current
one.
--
Nilay
On Tue, 23 Apr 2013, Beckmann, Brad wrote:
Hi Nilay,
Sorry I haven't been able to participate in a lot of the public gem5
discussion lately, but this is one item that I want to make time for.
We need to be careful when making this change. My primary concerns are
that we need to maintain that the ruby generated statistics are easily
readable and condense. Unlike simple stats that are primarily parsed by
scripts and used for graphs, ruby generated statistics are most useful
for debugging performance problems in the protocol. Therefore it is
important to make sure we can get a global idea of how the protocol is
behaving without having to scroll through hundreds or thousands of
lines. Ideally I would like to see us maintain the same format as they
are today with the per-controller counts and the summation all on the
same line.
Brad
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Nilay Vaish
Sent: Tuesday, April 23, 2013 12:01 PM
To: [email protected]
Subject: [gem5-dev] ruby: collecting cache controller statistics
Hi
I am thinking of allowing for using gem5's statistical variables within
coherence protocol definition files. I think this would help in getting
a better hold on how statistics are collected from the cache controllers
in coherence protocols. The current method of calling a function in to
the cache memory class is largely opaque and not well maintained. Since
we would like to move away from ruby's way of collecting statistics (at
some point in time), it seems to me this would be a better way than just
replacing 'int' variables with 'Counter' or 'Scalar' variables in ruby's
profiler class. Also, it seems that this would allow easier addition of
custom statistics that one might want to have.
Does any one has opinion on this issue?
Thanks
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
