cpu: o3: replace issueLatency with bool pipelined
Review Request #2745 - Created April 20, 2015 and submitted
| Information | |
|---|---|
| Nilay Vaish | |
| gem5 | |
| default | |
| Reviewers | |
| Default | |
Changeset 10791:d5f41246ec2e --------------------------- cpu: o3: replace issueLatency with bool pipelined Currently, each op class has a parameter issueLat that denotes the cycles after which another op of the same class can be issued. As of now, this latency can either be one cycle (fully pipelined) or same as execution latency of the op (not at all pipelined). The fact that issueLat is a parameter of type Cycles makes one believe that it can be set to any value. To avoid the confusion, the parameter is being renamed as 'pipelined' with type boolean. If set to true, the op would execute in a fully pipelined fashion. Otherwise, it would execute in an unpipelined fashion.
Posted (April 24, 2015, 1 a.m.)
-
src/cpu/o3/FuncUnitConfig.py (Diff revision 1) -
Perhaps this is not intentional, but the specific case highlights that it is in fact possible to have a value that is neither 1, nor the opLat.
Is there really no case where we want to say an operation takes X cycles and a new operation can be started every Y, with Y < X and Y > 1?