Hi gem5 users,
I am working with my team to set up a CPU model and I am having some trouble making sense of how the core settings are handled. The core configurations (for example, o3_arm_v7a.py [1]) allow (require?) specifying parameters for the various components (for example, size, associativity, etc. for the caches). I would expect those values to be used as defaults when using that core model unless anything else is specified on the command line. However, it seems that those values are always overridden with the default values for the command line parameters specified in Options.py [2] (for example, l2_size has a default value of 16MB, which will be used irrespective of what is defined in the configuration of the core). The consequence of this behavior is that I basically have to either remove the default values from Options.py or pass a long command-line configuration that reproduces exactly the default values I already specify in the core configuration. That seems rather inefficient to me. Is there a better way to handle those default parameters? If not, it would seem sensible to me to remove the default values from Options.py, so that defaults for the chose CPU type can be used. Thanks for any replies :-) -- dbb [1] https://github.com/gem5/gem5/blob/stable/configs/common/cores/arm/O3_ARM_v7a.py [2] https://github.com/gem5/gem5/blob/stable/configs/common/Options.py
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
