Hardware Reference
In-Depth Information
Fig. 7.4 Injection of
parameters in the virtual
platform
I top
I Node[0]
I LLC
I PktQueueManager
set_parameter (....)
MAX_CELLS
Table 7.3 Injection of parameters in the platform
cout < < “MULTI3 : Creating SCoPE XML plugin...” < < endl;
int status = uc_xml_init_plugin(argc, argv);
Get the parameters value using
MULTICUBE-SCoPE
I_top->I_Node[0]->I_LLC->i_PKTQueueManager-
>set_parameter(“MAX_CELLS”, ss_MAX_CELLS_PKT.str());
Use DS2_SC's API to inject
parameter in the platform
Through MULTICUBE-SCoPE the platform first obtains its parameters to be read.
Then, the plug-in reads the configuration file from modeFRONTIER and associates
a value to the parameter.
Next step is then to use DS2_SC APIs in order to modify the value of the internals
of the platform as shown in Fig. 7.4 .
To do so, the lines of code displayed in Table 7.3 are used.
Once a simulation finishes, the platform generates an XML file that is given as a
feedback to the modeFRONTIER tool. An example of such a file is shown below:
<?xml version="1.0" encoding="UTF-8"?>
<simulator_output_interface xmlns="http://www.multicube.eu/"
version="1.3">
<system_metric name="Power_Consumption"
value="1.752689280e-01"/>
<system_metric name="xput0_1" value="4.05376e+07"/>
<system_metric name="LatencyMin0_1" value="822.944"/>
<system_metric name="LatencyMax0_1" value="7107.76"/>
<system_metric name="LatencyMean0_1" value="22104.8"/>
<system_metric name="MaxJitter0_1" value="6284.82"/>
<system_metric name="xput1_0" value="810158"/>
<system_metric name="LatencyMin1_0" value="4114.55"/>
<system_metric name="LatencyMax1_0" value="11745.5"/>
<system_metric name="LatencyMean1_0" value="17720"/>
<system_metric name="MaxJitter1_0" value="7630.98"/>
</simulator_output_interface>
Finally, the last step of the process is to analyze the results thanks to the analysis
facilities provided by modeFRONTIER. In later sections of this study we will show
the main results of the process.
 
Search WWH ::




Custom Search