config: composing a single HMC device
Review Request #2936 - Created July 1, 2015 and discarded
| Information | |
|---|---|
| Erfan Azarkhish | |
| gem5 | |
| Reviewers | |
| Default | |
The main python script composing a single HMC device as a sub-system and specifying
all its parameters. I would like to mention that, one can easily instantiate multiple instances of the HMCSystem
class and build a network of HMCs, but this patch instantiates only one.
This patch and the subsequent chain of patches aim to model a simple Hybrid Memory Cube device in gem5
Please apply the complete chain before running the simulation.
Issue Summary
| Description | From | Last Updated | Status |
|---|---|---|---|
| I think this is fine for now. We could always make it four crossbars to capture the quadrants. | Andreas Hansson | July 1, 2015, 8:26 a.m. | Open |
| We should really do this using the clock domains of gem5. | Andreas Hansson | July 1, 2015, 8:26 a.m. | Open |
-
configs/common/HMC.py (Diff revision 1) -
I think this is fine for now. We could always make it four crossbars to capture the quadrants.
-
configs/common/HMC.py (Diff revision 1) -
We should really do this using the clock domains of gem5.
-
configs/common/HMC.py (Diff revision 1) -
response
-
configs/common/HMC.py (Diff revision 1) -
Either use the clock domains, or Param.Frequency
-
src/mem/SConscript (Diff revision 1) -
I would suggest to do this as part of the respective patches
-
src/mem/SConscript (Diff revision 1) -
Same as above
-
src/mem/SConscript (Diff revision 1) -
Same as above
