Power / PowerTable
Block Name: PowerTable

Code File Location: VisualSim/actor/lib/power/Power_Manager

Block Overview

• Study and model the power infrastructure
• Determine the consumption by operations on resources
• Design the best power management algorithm.
• To select appropriate battery configuration for a battery operated device 

Description

The PowerTable is used to optimize the system architecture with power as one of the metrics. The PowerTable works in conjunction with the Battery and energy harvesters are used to measure the power consumption, experiment power management algorithms, and size the battery and energy harvesters.  The Power platform in VisualSim works on the concept of dynamic state change and duration within a state for each device. The POwer Table works in conjunction with the timing of the model.  The Power Table does introduce a delay overhead reated to transition time between states.

Custom blocks: The custom block can be a single instance which has multiple states.  The power state is changed using the powerUpdate RegEx.  Custom devices can also be a block with multiple indentical instances within a single device. A good example are the Root Complex ports of the PCIe.  Here the ports differ in the number of lanes.  The power for different lanes counts would be the custom state columns- Active_4, Active_8 etc.  Each port is a queue number.  As each port receives a request, it can be added to the Power Table as a queue instance of the PCIe. This is done using the powerUpdateN RegEx operator. 

The Power Table supports the following blocks.  All others are treated as custom blocks.

    *  System_Resouce_Extend
    * System_Resource
    * Server- Single definition for all Queues. You cna change the state or the state power value for a single queue using the RegEx function-
    * Channel
    * Custom Device- Single
    * Custom Device-Multiple instances of same block.
    * Processor
    * Cache
    * Bus Controller
    * RAM
    * HW-DRAM
    * AXI Bus
    * AHB/APB

To illustrate the usage, look at the following Examples in the BDE.

• Multi-Core_DVFS_Design 

• Animation_Target_Processing

• Processor_Power_model

• Using Scheduler with Power

• Using Smart_Timed_Resource with Power

• SoC Power Management Algorithm

• Full SoC Power Exploration

• Hybrid Vehicle Power Generation, Management and Consumption

• SoC Power Measurement

Basic Facts about the PowerTable

1. 1. Maintains the power information for all the states of all the devices
2. 2. Maintains the statistics for all the devices
3. 3. Maintains the current power state of each device
4. 4. Handles the delay for power transition from one state to another
5. 5. Each window, hierarchy or class can have it's own Power Table.  The Power Table works hierarchically. All the tables of the lower level windows of a Hierarchy are added up to the next level Table. 
   
6. 6. Each device can have any number of power states.  The table can have 0.0 (not blank) for states that do not require any  state. 
   

Note: The user can add any number of Power States and Parameters.  The columns listed below are the minimum required.

Manager_Setup Table

 

 

Note: All units in the PowerTable configuration are in the Units of the parameter- Battery_Units.

The user can add any number of additional states to the device, E.g. Sleep, Deep_Sleep, etc.

Multiple lines associated with the HW_DRAM block:

--------- Name -----------   ---- Power State ---- Cycles -     */     Architecture_Block       Active  Standby   Down  Wait  Idle  Existing  OffState  OnState  t_OnOff      Mhz       Volts   ; ACT_Standby_DDR0                0.1     37.6   22.4  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* No Rd, Wr  */ ACT_Standby_DDR1                0.1     37.6   22.4  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* No Rd, Wr  */ ACT_Active_DDR0                20.6      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* No Rd, Wr  */ ACT_Active_DDR1                20.6      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* No Rd, Wr  */ WTR_Power_DDR0                115.8      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* Same as Wr */ WTR_Power_DDR1                115.8      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   /* Same as Wr */ Write_Power_DDR0              115.8      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; Write_Power_DDR1              115.8      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; Read_Power_DDR0               210.1      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; Read_Power_DDR1               210.1      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RRD_Power_DDR0                  7.4      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RRD_Power_DDR1                  7.4      0.0    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_0_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;   RFSH_Power_1_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_2_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_3_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_4_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_5_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_6_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_7_DDR0               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_0_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_1_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_2_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_3_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_4_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_5_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_6_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ; RFSH_Power_7_DDR1               6.4      6.3    0.0  0.0   0.0   Standby   Standby   Active   0.0        1000.0     1.0    ;

Multiple lines associated with AXI Bus

STR_TOP_LEVEL_AXI_Rd_Data_Channel     75.0     250.0    0.0      0.0     Standby   Standby   Active   1.0e-8    1000.0     1.0     ; STR_TOP_LEVEL_AXI_Wr_Data_Channel     75.0     200.0    0.0      10.0     Idle     Standby   Active    0.0       1000.0     1.0     ; Where the format is STR_ + AXI_Bus_Name + _Rd_Data_Channel is for rhe Read channel and STR_ + AXI_Bus_Name + _Wr_Data_Channel is for rhe Write channel

Mapping of Outputs to Units

 

RegEx Functions Description

Function 1:

powerManager(String Table_Name)
Eg: Result_A = powerManager("Manager_1")

Description: This is the PowerTable statistics. The output is a array of data structures.  Each data structure appears on a single line and has all the information on one device.  All device between this level of hierarchy are included in this table.  There is one data structure for each device.  Each data structure is identified by the name entered in the Manager_Setup. Each devices's data structure contains Device name, Time, Operating states,power states, transistion cycles, Parameters, etc. 
The final line row called total and contains the consolidation of all the devices.

{Scheduler_Sw1  = {Time = 1.000001, OffState = "Standby", t_Idle = 1.0E-6, Architecture_Block = "Scheduler_Sw1", t_Wait = 1.0E-6, Idle = 10.0, c_Standby = 7.0E-5, c_Active = 299.9999999999999, OnState = "Active", Volts = 1.0, t_Active = 1.0E-6, c_Idle = 0.0, Mhz = 1000.0, c_Wait = 0.0, Cumulative = 300.0000699999999, Average = 299.9997700002299, Standby = 70.0, t_Standby = 1.0E-6, Active = 300.0, Extend = false, NewState = "Standby", Wait = 0.0, Current = 70.0, Existing = "Standby"},
total                      = {Average = 299.9997700002299, Cumulative = 300.0000699999999, Time = 1.000001, Current = 70.0}}

Function 2:

stateChange(<Manager_Name> (String),  <Prefix + Block_Name>(String), <Operating_State>(String), <New_State>(String) )
Eg: Result_A = stateChange("Manager_1", "Scheduler_cpu", "Existing", "Idle")

Description: This function updates the specified opearing state to the New state specified in the function. The Manager_Name must match name in the PowerTable block, while the Block_Name (device name) must match the name (Appropriate Prefix + Block_Name) in the Manager_Setup table. Operating_State must be one of the three operating states, i.e. Existing, Onstate, or Offstate. New_State must be declared in the manager_Setup upfront. New_State can be one of the many power states. General power states are Active, Statndby, Wait, Idle.

Function 3:

updatePowerN (“STR_ServerName”, New State, (_queue_number+1))
Eg: Result_A = updatePowerN (“STR_Bus1, Active4, 5)

Description: This function works exclusively with the Server block.  This RegEx updates the power state for a single queue of the Server block.  The Block_Name (device name) must match a existng Server block in the model. Operating_State must be "Existing". New_State must be declared in the manager_Setup upfront. New_State can be one of the many power states. General power states are Active, Statndby, Wait, Idle.

Function 2:

Eg: Result_A = stateChange("Manager_1", "Scheduler_cpu", "Existing", "Idle")

Description: This function updates the specified opearing state to the New state specified in the function. The Manager_Name must match name in the PowerTable block, while the Block_Name (device name) must match the name (Appropriate Prefix + Block_Name) in the Manager_Setup table. Operating_State must be one of the three operating states, i.e. Existing, Onstate, or Offstate. New_State must be declared in the manager_Setup upfront. New_State can be one of the many power states. General power states are Active, Statndby, Wait, Idle.

Parameters

Manager_Setup

Manager_Setup consits the power values of the devices at different states. The Manager_Setup consists four different sections they are: Block name, Power States, Operating States, State Transitions and Parameters.
Block Names: These are the are names of the Architecture Blocks whose power consuption is to be monitored. PowerTable supports Processor, DRAM, Cache, BusArbiter, SystemResource, Queue and Servers by default as shown in the Table. Designer can declare his own device. Block Name must be a string
Power States: By default PowerTable provides Standby, Active, Wait and Idle power states. Designer can declare custom states like Sleep, Deep_Sleep etc. Values entered for these power states can either be double value or String. If it is a string it must be declared as a parameter in BDE, declared in the Expression_List section or a variable declared in the VariableList block.
Operating States: There are three states defined in Operating States, i.e. Existing, OffState and OnState. Exsting state corresponds to the initial state of the device during the simulation, by default this is set to Standby. Designer can change this state in the middle of the simulation according to the logic defined in the Expression_List window which will change the state of device at current time stamp. The default OnState is set to Active State. However an Architectur element like processor may have multiple active states while performing different tasks. E.g. if a processor has to execute different tasks say Task_1, Task_2, Task_3 and so on, during execution of each Task, processor will have different active states say Active_1, Active_2, Active_3 and so on, each Active states may have different power values; to accomplish this; state name is specified in OnState allowing that device to go to one of the active states. OnState of the device can be dynamically changed according to the tasks it is executing based on the logic defined in the Expression_List or using regEx function.
OffState is the state in which the device is not working and hence turned off; by default it is set to Standby.  
State names entered here must be String
State_Transistion: This specifies amount of time that the device will have to wait while going from one state to another state. By default Transition time for default states are defined E.g. t_Active, t_Standby etc. t_Active specifies the time delay from Active State to any other state. Similarly for other states also. Designer has to declare the transition time for custom States if declared any.  The Value entered can either be a double value or a string. If it is a string it must be defined as the parameter in BDE, in the Expression_List window or as a variable declared in the VariableList block.
Parameters: Any number of parameters can be defined in the Manager_Setup window. Example Mhz, LDO_Efficiency etc. Parameter declared here will be limited to the PowerTable. These paramters can be used for the computations and defining the logic.
Each line in the Manager_Set must end with a ';'

Note: In State_Transistion; if the delay is same for all the states one can use t_All as a replacement for individual states and can enter the value.

Async_State_Change

Async_State_Change window is used if the block changes its state asynchronously. The format is "<Device_Name>    <State>    <Time_or_Expression>     <Next_State>".  Device_Name is the name of the device whose state is to be changed asynchronously. State is the name of the device power state (Active, Standby, Wait, Idle etc.). Time_or_Expression specifies the maximum time for that device to stay in that State. Next_State specifies the next state that the device has to go to once the specified time is elapsed. Example, if the device (Scheduler_cpu) is in Standby state and it has to go to Idle state after 10ns if no change in the state occured; to accomplish this, one can define the following: "Scheduler_cpu  Standby    10.0e-9    Idle ; ".
Every single line must end with a ';'

Expression_List

Expression_List can be used to define the logic and declare the values that can be used elsewhere in the PowerTable. One can write as many expessions as needed. Like in an ExpressionList block, each expression must be a single line. Note that every expression must end with a ';'
The format for using Expression_List is "<Name>  <vaule or expression> ; ". Eg. " Cycle_t     1.0E-6 / Mhz ; " From this expression the value Cycle_t is computed which can be used for the State Transistion or Power States etc. the parameter Mhz can either be declared in Manager_Setup, as a parameter decalred outside of the block in the BDE or a variable declared in the VariableList.

Port

 

Created with the Personal Edition of HelpNDoc: Create help files for the Qt Help Framework