configs: set default cache params
Review Request #485 - Created Feb. 13, 2011 and submitted
| Information | |
|---|---|
| Korey Sewell | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
| ali, gblack, nate, stever | |
configs: set default cache params It's confusing (especially to new users), when you are setting some standard parameters (as defined in Options.py) and they aren't reflected in the simulations so we might as well link the settings in CacheConfig.py to those in Options.py
Posted (Feb. 14, 2011, 1:32 p.m.)
-
configs/common/CacheConfig.py (Diff revision 1) -
These lines look like they're too long. Since these are more complicated now, it might be a good idea to set up the two caches before the "if buildEnv[..." and then just pass them in to whichever function ends up being called.
Posted (Feb. 14, 2011, 9:24 p.m.)
Looks like a good idea.
-
configs/common/Options.py (Diff revision 1) -
Did you intend to change this default value too? If so, why?
Posted (Feb. 14, 2011, 11:26 p.m.)
I seem to have submitted a diff exactly like this.... Don't care who commits it if you want to go. The 64kB -> 32kB thing preserves the previous default config (although it probably changes Ruby's)