Changes between Version 21 and Version 22 of arch_info


Ignore:
Timestamp:
Apr 4, 2018, 9:39:38 AM (6 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • arch_info

    v21 v22  
    33[[PageOutline]]
    44
    5 ALMOS-MK has been designed to support clustered manycore architectures. It can be 32 bits cores (such as the MIPS32 based TSAR architecture), or 64 bits cores (such as the multi-cores Intel/AMD architectures). Each cluster containing at least one core, one physical memory bank, and an interrupt controller unit will host one kernel instance.
     5ALMOS-MKH has been designed to support clustered manycore architectures. It can be 32 bits cores (such as the MIPS32 based TSAR architecture), or 64 bits cores (such as the multi-cores Intel/AMD architectures). Each cluster containing at least one core, one physical memory bank, and an interrupt controller unit will host one kernel instance.
    66
    77All relevant parameters describing the clustered multi-core architecture must be defined in the binary '''arch_info.bin''' file.
    8 This binary file is exploited by the ALMOS-MK boot-loader to configure ALMOS-MK. It can be generated by a specific  '''arch_info.py''' python scrip, for each target architecture.
     8This binary file is exploited by the ALMOS-MKH boot-loader to configure ALMOS-MK. It can be generated by a specific  '''arch_info.py''' python scrip, for each target architecture.
    99
    1010== __1)  Cluster and cores identification__  ==
    … …  
    1212=== 1.1) Cluster identification ===
    1313
    14 To identify a cluster in the clustered architecture, ALMOS-MK uses an unique cluster identifier '''cxy'''. ALMOS-MK does not make any
     14To identify a cluster in the clustered architecture, ALMOS-MKH uses an unique cluster identifier '''cxy'''. ALMOS-MK does not make any
    1515assumption on the clusters topology, but makes the assumption that the '''cxy''' binary value can be directly concatenated to the local physical address (address inside a cluster) to build a global physical address. Warning: The cluster identifier '''cxy''' is NOT a continuous index, and cannot be used to index a cluster array.
    1616
    17 The size of the local physical address space (inside a cluster) is defined by a global parameter, that is the number of bits in a local physical address. The value of this parameter is 32 in architectures using 32 bits cores, but it can be larger in architectures using 64 bits cores. Any physical address is coded on 64 bits in ALMOS-MK.
     17The size of the local physical address space (inside a cluster) is defined by a global parameter, that is the number of bits in a local physical address. The value of this parameter is 32 in architectures using 32 bits cores, but it can be larger in architectures using 64 bits cores. A physical address is coded on 64 bits in ALMOS-MKH.
    1818
    1919Note : In architectures where the clusters are organized as a 2D mesh topology, is is generally possible to derive the [x,y] cluster coordinates from the '''cxy''' cluster identifier, and ALMOS-MK can use it to optimize placement and improve locality, but this optimisation is NOT mandatory, and ALMOS-MK supports architectures where the set of cluster is simply a linear vector of clusters.
    … …  
    2929== __2) Hardware architecture description__ ==
    3030
    31 For ALMOS-MK, the target hardware architecture is described in the binary file '''arch_info.bin'''.
    32 This file is loaded from disk by the ALMOS-MK boot-loader.
     31For ALMOS-MKH, the target hardware architecture is described in the binary file '''arch_info.bin'''.
     32This file is loaded from disk by the ALMOS-MKH boot-loader.
    3333
    3434=== 2.1) General assumptions ===
    … …  
    138138== __4) The boot_info_t structure__ ==
    139139
    140 The ALMOS-MK boot-loader  uses the informations found in '''arch_info.bin''' to build one '''boot_info_t''' structure in each cluster. This generic  '''boot_info_t''' structure is used by the ALMOS kernel to build in each cluster its own representation of the hardware.
     140The ALMOS-MKH boot-loader  uses the informations found in '''arch_info.bin''' to build one '''boot_info_t''' structure in each cluster. This generic  '''boot_info_t''' structure is used by the kernel to build in each cluster its own representation of the hardware.
    141141Therefore, the '''boot_info_t''' structure defines the generic (hardware independent) interface between the hardware specific boot-loader and the kernel. 
    142142