sanchayanmaity/gem5
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Ruby: Order profilers based on version

Browse source 
When Ruby stats are printed for events and transitions, they include stats
for all of the controllers of the same type, but they are not necessarily
printed in order of the controller ID "version", because of the way the
profilers were added to the profiler vector. This patch fixes the push order
problem so that the stats are printed in ascending order 0->(# controllers),
so statistics parsers may correctly assume the controller to which the stats
belong.
This commit is contained in:
Joel Hestness 2013-04-09 16:25:29 -05:00
parent 88d34665d0
commit b936619ab4
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
src/mem/slicc/symbols/StateMachine.py
View file

@ -1346,7 +1346,9 @@ ${ident}_ProfileDumper::${ident}_ProfileDumper()
void
${ident}_ProfileDumper::registerProfiler(${ident}_Profiler* profiler)
{
m_profilers.push_back(profiler);
if (profiler->getVersion() >= m_profilers.size())
m_profilers.resize(profiler->getVersion() + 1);
m_profilers[profiler->getVersion()] = profiler;
}
void
@ -1413,6 +1415,7 @@ class ${ident}_Profiler
public:
${ident}_Profiler();
void setVersion(int version);
int getVersion();
void countTransition(${ident}_State state, ${ident}_Event event);
void possibleTransition(${ident}_State state, ${ident}_Event event);
uint64 getEventCount(${ident}_Event event);
@ -1462,6 +1465,12 @@ ${ident}_Profiler::setVersion(int version)
m_version = version;
}
int
${ident}_Profiler::getVersion()
{
return m_version;
}
void
${ident}_Profiler::clearStats()
{