Searched refs:permissions (Results 1 – 13 of 13) sorted by relevance
| /arm-trusted-firmware-2.8.0/bl32/tsp/ |
| A D | ffa_helpers.c | 62 uint32_t receiver_count, ffa_mem_perm8_t permissions) in ffa_memory_region_init_header() argument
81 emad[i].mapd.memory_access_permissions = permissions; in ffa_memory_region_init_header()
98 ffa_mem_perm8_t permissions, in ffa_memory_retrieve_request_init() argument
103 receiver_count, permissions); in ffa_memory_retrieve_request_init()
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A D | security-advisory-tfv-3.rst | 29 contains flags to control data access permissions (``MT_RO``/``MT_RW``) and
30 instruction execution permissions (``MT_EXECUTE``/``MT_EXECUTE_NEVER``). Thus a
47 permissions separately to data access permissions. All RO normal memory regions
62 permissions but always leaves the memory as executable at Secure EL1.
|
| /arm-trusted-firmware-2.8.0/plat/nvidia/tegra/scat/ |
| A D | bl31.scat | 104 * individual permissions to them, so the actual alignment needed is 4K.
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | secure-partition-manager-mm.rst | 413 instruction access permissions.
416 permissions.
419 instruction access permissions.
422 instruction access permissions.
616 access permissions of the memory regions are statically provided by the platform
629 In this case, the Secure Partition needs a way to change the access permissions
758 permissions is prohibited. A request to mark a device memory region with
759 Executable permissions is prohibited.
|
| A D | xlat-tables-lib-v2-design.rst | 78 normal memory) as well as the memory access permissions (read-only or
113 access permissions. If the requested virtual and physical addresses mismatch
|
| A D | secure-partition-manager.rst | 718 permissions. Permissions are provided by invoking the interface
741 permissions to the sender.
919 Pair of interfaces to manage permissions to signal notifications. Prior to
1508 can use FF-A defined services (FFA_MEM_PERM_*) to update or change permissions
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | imx8m.rst | 98 pointers which are located in DRAM. Mapping DRAM without MT_RW permissions
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | security-hardening.rst | 82 there are two bits which determine the permissions of the counters:
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_spm.rst | 381 | | getting access or gaining permissions to a memory |
691 | | permissions to an unintended sender to set |
|
| A D | threat_model_el3_spm.rst | 333 | | getting access or gaining permissions to a memory |
|
| A D | threat_model.rst | 809 | Mitigations | When configuring access permissions, the |
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | firmware-design.rst | 2270 properties of the target memory region, such as its access permissions. The
2272 a memory page. Therefore, if software needs to set different permissions on two
2299 read-write permissions, whereas the code and read-only data below are configured
2312 of the access permissions for the code and read-only data. In this case,
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 3509 - Filter errors related to clock gate permissions
6023 specify the access permissions for instruction execution of a memory region.
|
Completed in 37 milliseconds