I strongly agree that any significant work on stats should be based on a strategy of unifying Ruby and gem5 stats. It's basically ridiculous to have two different stats packages in the same simulator, and to have to look in two different places for stats for no good reason. It was an OK situation as part of the merger transition, but it's unacceptable as the long-term status quo.
The whole point of the changes that Nate and Ali have worked on is to make the output format flexible. I have no particular love for the gem5 output format; the only original motivation was to make it look like SimpleScalar for backwards compatibility (as that was what we were transitioning away from at the time). I don't see that as a major factor anymore ;-). If we want to have an output format that looks like Ruby stats, and even declare that the new default, I would not oppose that, assuming there'd be a backwards compatibility option for those that have scripts that parse the old format. Steve On Tue, Jan 15, 2013 at 8:12 AM, Ali Saidi <[email protected]> wrote: > > > We'll be posting an updated version of the stats changes Nate posted > a while back using python as the outputter. With this framework you > should be able to do whatever kind of formatting you want. We've been > writing it into a SQLlite DB, as it's easier to parse after the fact if > you don't have to deal with string conversion and other text output > stuff. > > Ali > > On 15.01.2013 11:00, Jason Power wrote: > > > Hi Nilay, > > > > > Specifically on the issue of using gem5 stats vs keeping Ruby stats > > > a separate thing, how much work would it be to update gem5 stats to have > an > > option to output in a way that is more like the current ruby stats? > What's > > this work compared to the new functions for printing, clearing, > etc you're > > going to have to add to make the changes you're > suggesting? > > > > My opinion falls more in line with Andreas here. I > would love to be able to > > get all of the statistics generated in ruby > in gem5 stats, personally. > > Having unified statistics would be much > simpler IMO. Though, I definitely > > agree with the people who think that > the gem5 stats output is difficult for > > humans to read. > > > > Other than > the output format, are there any reasons not to use gem5 stats > > in > Ruby? > > > > Also, would the changes you are suggesting here make it > easier to move the > > statistics in ruby to gem5 stats? I would be good > with this change if it > > makes the transition easier to do later. > > > > > Jason > > > > On Tue, Jan 15, 2013 at 7:38 AM, Nilay Vaish > <[email protected]> wrote: > > > >> On Tue, 15 Jan 2013, Andreas Hansson > wrote: Hi Nilay, > >> > >>> That's fine. I just think there is value in > having one uniform stats framework, and if there is some serious work > being put into it, then basing it on gem5 stats seems like a sensible > choice from my point of view. We have some ongoing work to add a > database backend for the stats to simplify > storing/post-processing/**visualisation and obviously that would "just > work(?)" if the Ruby bits also used gem5 stats. No pressure, I merely > wanted understand and also let you know what changes are in the > pipeline. > >> Well, there are people who find processing / visualisation > with ruby stats easier. The reasoning behind this has more to do with > the format in which the file ruby.stats is generated, and less (or maybe > nothing at all) with how the stats are actually collected. -- Nilay > ______________________________**_________________ gem5-dev mailing list > [email protected] http://m5sim.org/mailman/ > [1]**listinfo/gem5-dev<http://m5sim.org/mailman/listinfo/gem5-dev [2]> > > > > > _______________________________________________ > > gem5-dev mailing > list > > [email protected] > > http://m5sim.org/mailman/listinfo/gem5-dev > [2] > > > > Links: > ------ > [1] http://m5sim.org/mailman/ > [2] > 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
