Difference between revisions of "CPU Models"
From gem5
| Line 4: | Line 4: | ||
* [[InOrder]] - Specific documentation on how all of the pipeline stages work, and how to modify and create new CPU models based on it. | * [[InOrder]] - Specific documentation on how all of the pipeline stages work, and how to modify and create new CPU models based on it. | ||
** [[InOrder Pipeline Stages | Pipeline Stages]] | ** [[InOrder Pipeline Stages | Pipeline Stages]] | ||
| − | ** [[InOrder Resource-Request Model]] | + | ** [[InOrder Resource-Request Model | Resource-Request Modeling]] |
| − | ** [[InOrder Resource Pool]] | + | ** [[InOrder Resource Pool | Resource Pool]] |
| − | ** [[InOrder Pipeline Description]] | + | ** [[InOrder Pipeline Description | Pipeline Description]] |
** [[InOrder ToDo List]] | ** [[InOrder ToDo List]] | ||
Revision as of 13:01, 12 January 2010
- SimpleCPU - A good place to start learning about how to fetch, decode, execute, and complete instructions in M5.
- O3CPU - Specific documentation on how all of the pipeline stages work, and how to modify and create new CPU models based on it.
- Checker - Details how to use it in your CPU model.
- InOrder - Specific documentation on how all of the pipeline stages work, and how to modify and create new CPU models based on it.
Supporting classes
- StaticInst - Used to hold static information and methods about specific binary instructions, such as addq's or subq's.
- DynInst - Used to hold dynamic information about instructions in the pipeline, such as the PC or predicted target.
- ThreadState - Used to store thread information that is generic across CPU models.
- SimpleThread - Used by simple CPU models to store architected state and provide the ThreadContext interface.
Interfaces
- ThreadContext - The ThreadContext class. Used to provide an interface for objects outside of the CPU to access the specific thread state.
- ExecContext - The ExecContext interface. An implicit interface that is used by the ISA in order to access the CPU's architected state.
