Lines Matching refs:boundary

288 The Isolation API operates on boundaries. A boundary represents a set of
290 boundary examples in the current implementation:
298     persistent after the initialization. This type of boundary needs the
301     is running. This type of boundary needs both set-up and switching
304 The boundary operations are abstracted as HAL interfaces because isolation
307   - The set-up HAL interface creates a partition boundary based on given
308     partition information. This created boundary is bound with the partition
309     for subsequent usage. The binding is done by storing the boundary into
311   - The activation HAL interface activates the partition boundary to secure
313     information and boundary are given to the activation HAL to accomplish
316 The data representing the partition boundary in runtime is defined with the
319   - It is required that one value represents one boundary. The different values
336 Multiple Secure Partitions can bind with the same boundary value. This
340 same domain does not need to change the activated boundary.
342 The boundary contains the partition's memory accessibility information, hence
343 memory access check shall be performed based on boundary.
441 - The boundary between the :term:`SPE` and the :term:`NSPE`
442 - The boundary to protect the SPM execution. For example, the PSA RoT
443   isolation boundary between the PSA Root of Trust and the Application Root of
469 This API binds partition with a platform-generated boundary. The boundary is
471 boundary is used in subsequent calls to `tfm_hal_activate_boundary()`_ when
472 boundary's owner partition get scheduled for running.
477 - ``p_boundary`` - Pointer for holding a partition's boundary.
481 - ``TFM_HAL_SUCCESS`` - The boundary has been bound successfully.
492                               uintptr_t boundary);
496 This API requires the platform to activate the boundary to ensure the given
499 The access permissions outside the boundary is platform-dependent.
504 - ``boundary`` - The boundary for the owner partition of ``p_ldinf``. This
509 - ``TFM_HAL_SUCCESS`` - the isolation boundary has been set up.
510 - ``TFM_HAL_ERROR_GENERIC`` - failed to set up the isolation boundary.
518   tfm_hal_status_t tfm_hal_memory_check(uintptr_t boundary,
526 access types in boundary. The boundary belongs to a partition which
531 - ``boundary`` - Boundary of a Secure Partition.
548 If the implementation chooses to encode a pointer as the boundary,
563 This API let the platform decide if a boundary switch is needed.
573 - ``false`` - No need for a boundary switch