inorder: stage width as a python parameter
allow the user to specify how many instructions a pipeline stage can process on any given cycle (stageWidth...i.e.bandwidth) by setting the parameter through the python interface rather than compile the code after changing the *.cc file. (we always had the parameter there, but still used the static 'ThePipeline::StageWidth' instead) - Since StageWidth is now dynamically defined, change the interstage communication structure to use a vector and get rid of array and array handling index (toNextStageIndex) since we can just make calls to the list for the same information
This commit is contained in:
@@ -40,7 +40,7 @@ class InOrderCPU(BaseCPU):
|
||||
threadModel = Param.ThreadModel('SMT', "Multithreading model (SE-MODE only)")
|
||||
|
||||
cachePorts = Param.Unsigned(2, "Cache Ports")
|
||||
stageWidth = Param.Unsigned(1, "Stage width")
|
||||
stageWidth = Param.Unsigned(4, "Stage width")
|
||||
|
||||
fetchMemPort = Param.String("icache_port" , "Name of Memory Port to get instructions from")
|
||||
dataMemPort = Param.String("dcache_port" , "Name of Memory Port to get data from")
|
||||
|
||||
Reference in New Issue
Block a user