| /trusted-firmware-m-latest/docs/integration_guide/ |
| D | spm_backends.rst | 13 - IPC Model
18 - SFN Model
23 Although the programming model is different, they share the same APIs to
35 contexts, which is required to support the IPC model Secure Partitions.
38 It can also adopt SFN model Secure Partitions.
45 Therefore, it can only adopt SFN model Secure Partitions.
56 | SPM backend | Supported Partition model | Supported Isolation Level |
66 If an implementation doesn't contain any IPC model Secure Partition and only
70 If an implementation contains any IPC model Secure Partition or requires
|
| D | tfm_secure_irq_integration_guide.rst | 17 Interrupt Handling Model
24 In this model, the interrupt handling is carried out immediately when the
32 In this model, the interrupt handling is deferred after the interrupt
46 While the SLIH is the only supported model for Secure Partitions which conform
122 The interrupt handling model is SLIH by default as it is the only supported one
170 The ``handling`` attribute specifies the interrupt handling model and must
|
| /trusted-firmware-m-latest/docs/design_docs/services/ |
| D | secure_partition_manager.rst | 61 Partition runtime model
64 `Inter-process communication` (`IPC`) model or `Secure Function` (`SFN`)
65 model.
67 A partition that runs under the `IPC` model looks like a classic `process`.
72 returned result to the client. The advantages of this model:
80 model converts multiple service accesses into messages, let the partition
83 The `Secure Function` (`SFN`) model partition is close to a `library`. Each
86 (from client to service function) is a function call. This model:
96 resource-constrained devices, it is called an `SFN model implementation`. And
97 it is an `IPC model implementation` when `IPC` partitions exist in the system.
[all …]
|
| /trusted-firmware-m-latest/secure_fw/spm/include/ffm/ |
| D | backend.h | 26 * Runtime model-specific component initialization routine. This
33 * Runtime model-specific kick-off method for the whole system.
39 /* Runtime model-specific message handling mechanism. */
43 * Runtime model-specific message replying.
|
| /trusted-firmware-m-latest/tools/ |
| D | tfm_parse_manifest_list.py | 38 ffm_manifest_attributes = ['psa_framework_version', 'name', 'type', 'priority', 'model', 'entry_poi…
130 # For 1.0 Partition, the model is IPC
131 manifest['model'] = 'IPC'
133 # "model" validation:
134 model = manifest.get('model', None)
135 if model == None:
136 raise Exception('{} is missing the "model" attribute'.format(manifest['name']))
139 if model == 'IPC':
144 elif model == 'SFN':
150 raise Exception('Invalid "model" of {}'.format(manifest['name']))
[all …]
|
| /trusted-firmware-m-latest/docs/integration_guide/services/ |
| D | tfm_secure_partition_addition.rst | 19 IPC model The secure IPC framework
25 SFN model Secure Function model
49 If not otherwise specified, the steps are identical for IPC and SFN model.
51 The IPC and SFN model conforms to the *PSA Firmware Framework for M (FF-M) v
98 Here is a manifest reference example for the IPC model:
101 To use SFN model, the user needs to replace ``"model": "IPC"`` to
102 ``"model": "SFN"``. The user also needs to remove the attribute
112 "model": "IPC",
471 Entry point for IPC Model Partitions
504 Entry init for SFN Model Partitions
[all …]
|
| /trusted-firmware-m-latest/config/ |
| D | pre_config.cmake | 18 message(FATAL_ERROR "Library Model is deprecated, please DO NOT use TFM_LIB_MODEL anymore."
19 "SFN model is a replacement for Library Model.
20 You can use -DCONFIG_TFM_SPM_BACKEND=SFN to select SFN model.")
|
| D | set_config.cmake | 29 # Load TF-M model specific default config
34 # Also select IPC model by default for multi-core platforms that enable TrustZone.
|
| /trusted-firmware-m-latest/docs/releases/ |
| D | 1.6.0.rst | 12 - Enabled Secure Function (SFN) Model Partition compliance in IPC backend.
15 - The following Secure Partitions are converted to SFN model:
21 - FF-M v1.1 SFN Model supported in Profile Small.
22 - HAL Separation of Library Model and IPC/SFN backend.
|
| /trusted-firmware-m-latest/tools/templates/ |
| D | partition_load_info.template | 48 {% if config_impl['CONFIG_TFM_SPM_BACKEND_IPC'] == '1' or manifest.model == "IPC" %}
52 {% if manifest.model == "IPC" %}
112 {% if manifest.model == "IPC" %}
123 {% if config_impl['CONFIG_TFM_SPM_BACKEND_IPC'] == '1' or manifest.model == "IPC" %}
138 {% if config_impl['CONFIG_TFM_SPM_BACKEND_IPC'] == '1' or manifest.model == "IPC" %}
161 {% if manifest.model == "SFN" %}
167 {% if manifest.model == "SFN" %}
|
| D | manifestfilename.template | 17 {% if manifest.model == "SFN" %}
27 {% if manifest.model == "SFN" %}
|
| /trusted-firmware-m-latest/docs/security/security_advisories/ |
| D | fwu_write_vulnerability.rst | 15 | Configurations | IPC model with Firmware Update partition enabled |
17 | Impact | In IPC model, the caller of ``psa_fwu_write()`` from SPE |
53 In IPC model, this service calls the ``tfm_fwu_write_ipc()`` API to write
64 In IPC model, the caller of ``psa_fwu_write()`` from SPE or NSPE can overwrite
|
| D | svc_caller_sp_fetching_vulnerability.rst | 6 | | IPC model to behave unexpectedly. |
15 | Configurations | IPC Model on Armv8-M |
59 SVC functionalities. The following section analysis impact of the IPC model.
60 Library model is not vulnerable to this attack because it checks the PE mode
|
| D | stack_seal_vulnerability.rst | 55 stack depending on whether TF-M is in library mode or IPC model. When the
88 The interrupt handling in IPC model uses PSA signal to signal the partition
91 during interrupt handling in IPC model, there is no additional threat caused
|
| /trusted-firmware-m-latest/interface/include/psa/ |
| D | crypto_driver_common.h | 11 * This file is part of the PSA Crypto Driver Model, containing functions for
14 * comprising the driver model, which driver authors implement, are not
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA5/ |
| D | model_config.txt | 5 … # (bool , init-time) default = '1' : Set whether the model has VFP support
6 … # (bool , init-time) default = '1' : Set whether model has NEON support
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA9/ |
| D | model_config.txt | 5 … # (bool , init-time) default = '1' : Set whether the model has VFP support
6 … # (bool , init-time) default = '1' : Set whether model has NEON support
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CA7/ |
| D | model_config.txt | 5 … # (bool , init-time) default = '1' : Set whether CT model has been built wit…
6 … # (bool , init-time) default = '1' : Set whether CT model has been built wit…
|
| /trusted-firmware-m-latest/docs/configuration/profiles/ |
| D | tfm_profile_small.rst | 28 - Secure Function (SFN) model [2]_
74 TF-M framework model
77 SFN model is selected by default in Profile Small implementation.
78 SFN model is defined in FF-M 1.1 extensions [2]_. It is a more simple
80 with Inter-Process Communication (IPC) model [3]_.
85 PSA Security Model [4]_ defines 3 levels of isolation.
94 Profile Small dedicated use cases with simple service model may not require
364 The top-level Profile Small CMake config file selects SFN model and level 1
367 In SFN model, ``-DPSA_FRAMEWORK_HAS_MM_IOVEC`` is enabled by default.
543 SFN model is selected by default.
[all …]
|
| D | tfm_profile_medium.rst | 22 - Inter-Process Communication (IPC) model [PSA-FF-M]_
66 Profile Medium with IPC model and isolation level 2 aims to support usage
67 scenarios which require more complicated secure service model and additional
77 IPC model
80 Profile Medium enables IPC model by default. IPC model can achieve a more
82 footprint and bring in longer latency, compared to SFN model.
84 TF-M IPC model implementation follows the PSA Firmware Framework for M
263 partitions. Because Profile Medium enables IPC model, the IPC tests are also
|
| /trusted-firmware-m-latest/docs/getting_started/ |
| D | tfm_getting_started.rst | 307 Run the sample code on SSE-200 Fast-Model, using FVP_MPS2_AEMv8M provided by
319 1. install Arm Development Studio to get the fast-model.
352 To automatically terminate the fast-model when it finishes running,
361 1. install Arm Development Studio to get the fast-model.
387 To automatically terminate the fast-model when it finishes running,
|
| /trusted-firmware-m-latest/docs/security/threat_models/ |
| D | index.rst | 4 Threat model <generic_threat_model.rst>
|
| /trusted-firmware-m-latest/secure_fw/spm/core/ |
| D | interrupt.c | 171 /* SLIH Model Handling */ in spm_handle_interrupt()
175 /* FLIH Model Handling */ in spm_handle_interrupt()
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM55/ |
| D | model_config.txt | 6 … # (bool , init-time) default = '1' : Set whether the model has VFP support
7 … # (int , init-time) default = '0x1' : Set whether the model has MVE support. I…
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Layer/Target/CM55NS/ |
| D | model_config.txt | 6 … # (bool , init-time) default = '1' : Set whether the model has VFP support
7 … # (int , init-time) default = '0x1' : Set whether the model has MVE support. I…
|
