----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/1606/#review3847 -----------------------------------------------------------
configs/common/Options.py <http://reviews.gem5.org/r/1606/#comment3709> Why do we need this separately? Why not just add the list of configurations to help text for cpu-type? - Nilay Vaish On Jan. 7, 2013, 11:30 a.m., Ali Saidi wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/1606/ > ----------------------------------------------------------- > > (Updated Jan. 7, 2013, 11:30 a.m.) > > > Review request for Default. > > > Description > ------- > > Changeset 9455:969ab2ed5cfa > --------------------------- > config: Cleanup CPU configuration > > The CPUs supported by the configuration scripts used to be > hard-coded. This was not ideal for several reasons. For example, the > configuration scripts depend on all CPU models even though only a > subset might have been compiled. > > This changeset adds a new module to the configuration scripts that > automatically discovers the available CPU models from the compiled > SimObjects. As a nice bonus, the use of introspection allows us to > automatically generate a list of available CPU models suitable for > printing. This list is augmented with the Python doc string from the > underlying class if available. > > > Diffs > ----- > > configs/common/CpuConfig.py PRE-CREATION > configs/common/Options.py 56610ab73040 > configs/common/Simulation.py 56610ab73040 > > Diff: http://reviews.gem5.org/r/1606/diff/ > > > Testing > ------- > > > Thanks, > > Ali Saidi > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
