config: Use shared cache config for regressions
Review Request #1481 - Created Oct. 24, 2012 and submitted
| Information | |
|---|---|
| Andreas Hansson | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 9314:f63537293334 --------------------------- config: Use shared cache config for regressions This patch uses the common L1, L2 and IOCache configuration for the regressions that all share the same cache parameters. There are a few regressions that use a slightly different configuration (memtest, o3-timing=mp, simple-atomic-mp and simple-timing-mp), and the latter are not changed in this patch. They will be updated in a future patch. The common cache configurations are changed to match the ones used in the regressions, and are slightly changed with respect to what they were. Hopefully this means we can converge on a common base configuration, used both in the normal user configurations and regressions. As only regressions that shared the same cache configuration are updated, no regressions are affected.
util/regress all passing (disregarding t1000 and eio)
Ship It!
not sure my the 92 is tehre ,but overall it looks like a noble effort.
-
configs/common/Caches.py (Diff revision 1) -
92?
Posted (Oct. 24, 2012, 4:32 p.m.)
-
configs/common/Caches.py (Diff revision 1) -
Indeed...92! This is what all the affected regressions used until this point. At least now we can change it in a single location, and also unify this with the remaining three regressions that are slightly less aggressive on this front. Next patch :)