Changes between Version 19 and Version 20 of arch_info
- Timestamp:
- Aug 4, 2017, 3:13:25 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
arch_info
v19 v20 3 3 [[PageOutline]] 4 4 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 I NTEL/AMD architectures). Each cluster containing at least one core, one physical memory bank, and an interrupt controller unit will host one kernel instance.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. 6 6 7 7 All relevant parameters describing the clustered multi-core architecture must be defined in the binary '''arch_info.bin''' file. … … 13 13 14 14 To identify a cluster in the clustered architecture, ALMOS-MK uses an unique cluster identifier '''cxy'''. ALMOS-MK does not make any 15 assumption on the clusters topology, but makes the assumption that the '''cxy''' binary value can be directly concaten ed 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.15 assumption 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. 16 16 17 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. … … 50 50 * some devices contains a variable number of input IRQs. 51 51 52 An ad ressable device can be a physical memory bank, or a peripheral containing addressable registers.52 An addressable device can be a physical memory bank, or a peripheral containing addressable registers. 53 53 54 54 The '''arch_info.bin''' BLOB is organised as the concatenation of a fixed size header, and 4 variable size arrays of fixed size objects: … … 108 108 || '''ptype''' || Peripheral type || 109 109 || '''channels''' || number of channels for multi-channels peripherals || 110 || '''arg0''' || option nal argument depending on peripheral type ||111 || '''arg1''' || option nal argument depending on peripheral type ||112 || '''arg2''' || option nal argument depending on peripheral type ||113 || '''arg3''' || option nal argument depending on peripheral type ||110 || '''arg0''' || optional argument depending on peripheral type || 111 || '''arg1''' || optional argument depending on peripheral type || 112 || '''arg2''' || optional argument depending on peripheral type || 113 || '''arg3''' || optional argument depending on peripheral type || 114 114 115 115 The peripheral type defines actually a composite index containing a functional type (func-type), and an implementation type (impl_type).
