Changes between Version 13 and Version 14 of mapping_info


Ignore:
Timestamp:
Oct 27, 2014, 5:48:07 PM (10 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • mapping_info

    v13 v14  
    8282The physical global processor index will be : ( ( x << y_width ) + y ) << p_width ) + p
    8383
    84 === Physical memory bank ===
     84=== 3. Physical memory bank ===
    8585
    8686The '''mapping.addRam( )''' construct define one physical memory bank, and the associated physical segment in a cluster. It has the following arguments:
     
    9191The target cluster coordinates (x,y) is defined by the base address MSB bits.
    9292
    93 === 3. Physical peripheral ===
     93=== 4. Physical peripheral ===
    9494
    9595The '''mapping.addPeriph( )''' construct adds one peripheral, and the associated physical segment in a cluster. It has the following arguments:
     
    105105The supported peripheral types and subtypes are defined in the [source:soft/giet_vm/giet_python/mapping.py mapping.py] file.
    106106
    107 === 4. Interrupt line ===
     107=== 5. Interrupt line ===
    108108
    109109The '''mapping.addIrq()''' construct adds one IRQ line input to an XCU peripheral, or to a PIC peripheral. It has the following arguments:
     
    139139The ''x'', ''y'', and ''pseg'' arguments define actually the mapping.
    140140
    141 === Boot vsegs ===
     141=== 1. Boot vsegs ===
    142142
    143143There is 4 'vsegs for the GIET_VM bootloader:
     
    148148These 4 vsegs must be identity mapping (because the page table are not available), and are mapped in the first big physical page (2 Mbytes) in cluster [0][0].
    149149
    150 === Kernel vsegs ===
     150=== 2. Kernel vsegs ===
    151151
    152152There is six types of vsegs for the GIET_VM kernel, but some vsegs are replicated in all clusters, to improve locality and minimize contention, as explained below:
     
    156156 * The '''seg_kernel_sched_x_y''' vseg has type SCHED. It contains the processor schedulers (one scheduler per processor). There is one such vseg in each cluster, and it must be mapped on small pages (two small pages per scheduler).
    157157
    158 === Peripheral vsegs ===
     158=== 3. Peripheral vsegs ===
    159159
    160160A global vseg must be defined for each addressable peripheral.
     
    174174 * One or several '''mwmr''' vseg(s)
    175175 
    176 === create the vspace ===
     176=== 1. create the vspace ===
    177177
    178178The '''mapping.addvspace( )''' construct define a vspace. It has the following arguments:
     
    180180|| startname || name of              ||
    181181
    182 ===  vseg mapping ===
     182===  2. vseg mapping ===
    183183
    184184The '''mapping.addVseg( )''' construct define the mapping of a vseg in the vspace. It has the following arguments:
     
    200200The ''x'', ''y'', and ''pseg'' arguments define actually the mapping.
    201201
    202 === task mapping ===
     202=== 3. task mapping ===
    203203
    204204The '''mapping.addVseg( )''' construct  define the mapping of  a task in the vspace. It has the following arguments: