| /trusted-firmware-a/plat/common/ |
| A D | plat_bl_common.c | 116 const mmap_region_t *regions = bl_regions; in setup_page_tables() local
118 while (regions->size != 0U) { in setup_page_tables()
120 regions->base_va, in setup_page_tables()
121 regions->base_va + regions->size, in setup_page_tables()
122 regions->attr); in setup_page_tables()
123 regions++; in setup_page_tables()
|
| /trusted-firmware-a/plat/rpi/rpi3/ |
| A D | rpi3_bl31_setup.c | 161 int i, regions, rc; in rpi3_dtb_add_mem_rsv() local
171 regions = fdt_num_mem_rsv(dtb); in rpi3_dtb_add_mem_rsv()
173 VERBOSE("rpi3: Found %d mem reserve region(s)\n", regions); in rpi3_dtb_add_mem_rsv()
176 if (regions < 1) in rpi3_dtb_add_mem_rsv()
184 for (i = 0; i < regions; i++) { in rpi3_dtb_add_mem_rsv()
201 if (i == regions) { in rpi3_dtb_add_mem_rsv()
|
| /trusted-firmware-a/docs/components/ |
| A D | xlat-tables-lib-v2-design.rst | 59 `mmap` regions
148 * The maximum number of `mmap` regions to map.
176 - number of `mmap` regions: ``MAX_MMAP_REGIONS``;
184 Static and dynamic memory regions
197 - *Dynamic regions* can be added or removed any time.
242 contrast with the dynamic regions APIs (for example
254 #. Add some static regions, add some dynamic regions.
260 regions can still be added or removed.
283 Dynamic regions are not allowed to overlap each other. Static regions are
331 From mmap regions to translation tables
[all …]
|
| A D | granule-protection-tables-design.rst | 51 small regions (granules) of memory can be assigned to different PAS with a 2
75 desired PAS regions is passed into the library which validates the mappings,
88 Defining PAS regions
149 are then added to the L1 PAS regions to be initialized in the next step and
184 * ``GPCCR_L0GPTSZ_30BITS`` (1GB regions, 0x40000000 bytes)
185 * ``GPCCR_L0GPTSZ_34BITS`` (16GB regions, 0x400000000 bytes)
186 * ``GPCCR_L0GPTSZ_36BITS`` (64GB regions, 0x1000000000 bytes)
187 * ``GPCCR_L0GPTSZ_39BITS`` (512GB regions, 0x8000000000 bytes)
|
| A D | secure-partition-manager-mm.rst | 58 - Memory and device regions in the system address map.
173 - ``plat_get_secure_partition_mmap()`` returns an array of mmap regions that
174 describe the memory regions that the SPM needs to allocate for a Secure
412 1. Device regions are mapped with nGnRE attributes and Execute Never
418 3. Read Only data memory regions are mapped with RO data and Execute Never
421 4. Read Write data memory regions are mapped with RW data and Execute Never
425 regions then all memory regions will be marked with Code memory region
607 The SPM is responsible for enabling access to regions of memory in the system
608 address map from a Secure Partition. This is done by mapping these regions in
630 of its memory regions. The SPM provides this feature through the
[all …]
|
| A D | ffa-manifest-binding.rst | 103 - value type: "memory-regions" node
104 - Specific "memory-regions" nodes that describe the RX/TX buffers expected
159 - Must be the string "arm,ffa-manifest-memory-regions".
195 - Must be the string "arm,ffa-manifest-device-regions".
|
| A D | secure-partition-manager.rst | 499 The SP manifest may contain memory and device regions nodes. In case of
502 - Memory regions are mapped in the SP EL1&0 Stage-2 translation regime at
504 specify RX/TX buffer regions in which case it is not necessary for an SP
506 - Device regions are mapped in the SP EL1&0 Stage-2 translation regime (or
896 Secure and non-secure IPA regions use the same set of Stage-2 page tables within
1174 management transactions on their behalf. The acccess to the MMIO regions of
1228 for memory regions.
|
| A D | realm-management-extension.rst | 29 memory regions as Root or Realm respectively.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | xlat-tables-lib-v2-design.rst.txt | 59 `mmap` regions
148 * The maximum number of `mmap` regions to map.
176 - number of `mmap` regions: ``MAX_MMAP_REGIONS``;
184 Static and dynamic memory regions
197 - *Dynamic regions* can be added or removed any time.
242 contrast with the dynamic regions APIs (for example
254 #. Add some static regions, add some dynamic regions.
260 regions can still be added or removed.
283 Dynamic regions are not allowed to overlap each other. Static regions are
331 From mmap regions to translation tables
[all …]
|
| A D | granule-protection-tables-design.rst.txt | 51 small regions (granules) of memory can be assigned to different PAS with a 2
75 desired PAS regions is passed into the library which validates the mappings,
88 Defining PAS regions
149 are then added to the L1 PAS regions to be initialized in the next step and
184 * ``GPCCR_L0GPTSZ_30BITS`` (1GB regions, 0x40000000 bytes)
185 * ``GPCCR_L0GPTSZ_34BITS`` (16GB regions, 0x400000000 bytes)
186 * ``GPCCR_L0GPTSZ_36BITS`` (64GB regions, 0x1000000000 bytes)
187 * ``GPCCR_L0GPTSZ_39BITS`` (512GB regions, 0x8000000000 bytes)
|
| A D | secure-partition-manager-mm.rst.txt | 58 - Memory and device regions in the system address map.
173 - ``plat_get_secure_partition_mmap()`` returns an array of mmap regions that
174 describe the memory regions that the SPM needs to allocate for a Secure
412 1. Device regions are mapped with nGnRE attributes and Execute Never
418 3. Read Only data memory regions are mapped with RO data and Execute Never
421 4. Read Write data memory regions are mapped with RW data and Execute Never
425 regions then all memory regions will be marked with Code memory region
607 The SPM is responsible for enabling access to regions of memory in the system
608 address map from a Secure Partition. This is done by mapping these regions in
630 of its memory regions. The SPM provides this feature through the
[all …]
|
| A D | ffa-manifest-binding.rst.txt | 103 - value type: "memory-regions" node
104 - Specific "memory-regions" nodes that describe the RX/TX buffers expected
159 - Must be the string "arm,ffa-manifest-memory-regions".
195 - Must be the string "arm,ffa-manifest-device-regions".
|
| A D | secure-partition-manager.rst.txt | 499 The SP manifest may contain memory and device regions nodes. In case of
502 - Memory regions are mapped in the SP EL1&0 Stage-2 translation regime at
504 specify RX/TX buffer regions in which case it is not necessary for an SP
506 - Device regions are mapped in the SP EL1&0 Stage-2 translation regime (or
896 Secure and non-secure IPA regions use the same set of Stage-2 page tables within
1174 management transactions on their behalf. The acccess to the MMIO regions of
1228 for memory regions.
|
| A D | realm-management-extension.rst.txt | 29 memory regions as Root or Realm respectively.
|
| /trusted-firmware-a/lib/utils/ |
| A D | mem_region.c | 56 void clear_map_dyn_mem_regions(struct mem_region *regions, in clear_map_dyn_mem_regions() argument
66 assert(regions != NULL); in clear_map_dyn_mem_regions()
71 begin = regions[i].base; in clear_map_dyn_mem_regions()
72 size = regions[i].nbytes; in clear_map_dyn_mem_regions()
|
| /trusted-firmware-a/plat/arm/board/fvp/fdts/ |
| A D | optee_sp_manifest.dts | 35 device-regions {
36 compatible = "arm,ffa-manifest-device-regions";
|
| /trusted-firmware-a/plat/rpi/rpi4/ |
| A D | rpi4_bl31_setup.c | 216 int regions = fdt_num_mem_rsv(dtb); in remove_spintable_memreserve() local
219 for (i = 0; i < regions; i++) { in remove_spintable_memreserve()
|
| /trusted-firmware-a/include/lib/ |
| A D | utils.h | 37 void clear_map_dyn_mem_regions(struct mem_region *regions,
|
| /trusted-firmware-a/docs/security_advisories/ |
| A D | security-advisory-tfv-3.rst | 47 permissions separately to data access permissions. All RO normal memory regions
66 - The xlat\_tables library ensures that all Read-Write (RW) memory regions are
|
| A D | security-advisory-tfv-1.rst | 154 regions mapped in by ARM platforms. Here, ``mem_size`` may be the
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/security_advisories/ |
| A D | security-advisory-tfv-3.rst.txt | 47 permissions separately to data access permissions. All RO normal memory regions
66 - The xlat\_tables library ensures that all Read-Write (RW) memory regions are
|
| A D | security-advisory-tfv-1.rst.txt | 154 regions mapped in by ARM platforms. Here, ``mem_size`` may be the
|
| /trusted-firmware-a/fdts/ |
| A D | n1sdp-multi-chip.dts | 95 #redistributor-regions = <2>;
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model.rst.txt | 592 | | and sizes identifying memory regions, are |
716 | | library provides APIs to define memory regions |
721 | | memory regions. When assigning access |
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model.rst | 592 | | and sizes identifying memory regions, are |
716 | | library provides APIs to define memory regions |
721 | | memory regions. When assigning access |
|