Recent changes to Configuration

Configuration modified by Claudio Scordino

Claudio Scordino — Mon, 29 Apr 2013 13:45:45 -0000

--- v3
+++ v4
@@ -33,20 +33,9 @@
 Note that in this example:

 * the architecture contains only one processor, of type *"mycpu"*
-* the file related to the data memory exported by the kernel driver is *''/dev/mycpu-dmemory.0''*
-* the result of the computation can be found at address 0
-* the offset of the input file for data memory is 288; this depends on the compiler used.
-* the file related to the instruction memory exported by the kernel driver is *''/dev/mycpu-imemory.0''*
-* the file related to the status register exported by the kernel driver is *''/sys/devices/virtual/mycpu_core/mycpu-smemory.0/mycpu_core_status''*. In this file:
-    * 1 means that the computation has finished
-    * 2 means that the processor is idle
-    * 4 means that an exception happened
-    * 8 means that the processor has been preempted
-* the file related to the control register exported by the kernel driver is *''/sys/devices/virtual/mycpu_core/mycpu-smemory.0/mycpu_core_ctl''*. For this file:
-    * Writing 1 starts the processor
-    * Writing 2 stops the processor
-    * Writing 4 preempts the processor
-* The processor has a set of reconfigurable properties (i.e., issuewidth and cache block) each one with an initial setting and a file to trigger the reconfiguration.
+* the file related to the data memory exported by the kernel driver is *''/dev/mycpu.0-dmemory.0''*
+* similarly, the file related to the instruction memory exported by the kernel driver is *''/dev/mycpu.0-imemory.0''*
+* The processor has a set of reconfigurable properties (i.e., issuewidth and cache size) each one with an initial setting and a file to trigger the reconfiguration.

 This file must be written based on files/values exported by your specific kernel driver, of course. The file is read by the Supervisor only once, during the boot.

Configuration modified by Claudio Scordino

Claudio Scordino — Mon, 29 Apr 2013 13:44:31 -0000

--- v2
+++ v3
@@ -11,14 +11,24 @@
     
     
     
-        
-        
-        
-        
-        
-        
+        
+            
+        
+        
+            
+            
+        
     
     
+    

 Note that in this example:

WikiPage Configuration modified by Claudio Scordino

Claudio Scordino — Wed, 27 Jun 2012 13:22:22 -0000

--- v1
+++ v2
@@ -1,7 +1,7 @@
 Configuration of SC-REX
 =======================
 
-This Section explains how to configure SC_REX, assumeing that SC-REX has been already built and installed as explained in Section [Install].
+This Section explains how to configure SC_REX, assuming it has been already built and installed as explained in Section [Install].
 
 ###Architecture file###

WikiPage Configuration modified by Claudio Scordino

Claudio Scordino — Wed, 27 Jun 2012 13:15:14 -0000

Configuration of SC-REX ======================= This Section explains how to configure SC_REX, assumeing that SC-REX has been already built and installed as explained in Section [Install]. ###Architecture file### The XML file of the architecture is located in */etc/screx/architecture.xml* and describes the underlying architecture (i.e., the set of reconfigurable devices, their properties, the files to access memories and to modify each property). The XML file has a structure similar to the following example: Note that in this example: * the architecture contains only one processor, of type *"mycpu"* * the file related to the data memory exported by the kernel driver is *''/dev/mycpu-dmemory.0''* * the result of the computation can be found at address 0 * the offset of the input file for data memory is 288; this depends on the compiler used. * the file related to the instruction memory exported by the kernel driver is *''/dev/mycpu-imemory.0''* * the file related to the status register exported by the kernel driver is *''/sys/devices/virtual/mycpu_core/mycpu-smemory.0/mycpu_core_status''*. In this file: * 1 means that the computation has finished * 2 means that the processor is idle * 4 means that an exception happened * 8 means that the processor has been preempted * the file related to the control register exported by the kernel driver is *''/sys/devices/virtual/mycpu_core/mycpu-smemory.0/mycpu_core_ctl''*. For this file: * Writing 1 starts the processor * Writing 2 stops the processor * Writing 4 preempts the processor * The processor has a set of reconfigurable properties (i.e., issuewidth and cache block) each one with an initial setting and a file to trigger the reconfiguration. This file must be written based on files/values exported by your specific kernel driver, of course. The file is read by the Supervisor only once, during the boot. ###Reconfiguration tables### The XML file for the reconfiguration allows to understand the new configuration for each property of each reconfigurable device given the information about QoS and phase received at run-time by the application. It's a sort of "big table" written in XML. The XML file has a structure similar to the following example: Some examples of these files can be found inside the */etc/screx/* directory. The absolute path of the file is communicated by the application whenever it sends a request for a new task to the supervisor.