Changes between Version 37 and Version 38 of boot_procedure


Ignore:
Timestamp:
Jun 29, 2018, 4:21:01 PM (7 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • boot_procedure

    v37 v38  
    77The ALMOS-MKH boot procedure can be decomposed in two phases:
    88 * The architecture dependent phase, implemented by an architecture specific '''boot_loader''' procedure.
    9  * The architecture independent phase, implemented by a generic '''kernel-init''' procedure.
     9 * The architecture independent phase, implemented by a generic (architecture independent) '''kernel-init''' procedure.
    1010
    1111As the generic (i.e. architecture independent) kernel initialization procedure is executed in parallel by all kernel instances in all clusters containing at least one core and one memory bank, the main task of the boot-loader is to load - in each cluster - a local copy of
    … …  
    5252In all clusters, the core with local index 0 is called ''CP0''.
    5353
    54 We describe below the four boot phases :
    55 
    56 Le chargement d'ALMOS-MK sur l'architecture TSAR se fait donc en 4 phases décrites ci-dessous
     54We describe below the four phases for the TSAR boot-loader:
    5755
    5856=== B1. Preloader phase ===
    … …  
    6462
    6563All cores execute the same preloader code, but the work done depends on the core identifier. The core[0][0] (i.e. CP0 in cluster 0) load
    66 in local memory of cluster 0, at address the boot loader code. All other cores do only one task before going to sleep (low-power) state:
     64in local memory of cluster 0, the boot-loader code. All other cores do only one task before going to sleep (low-power) state:
    6765each core activates its private WTI channel in the local ICU (Interrupt Controller Unit) to be wake-up by core [0][0], using an
    6866IPI (Inter Processor Interrupt).