Searched refs:SMC (Results 1 – 25 of 82) sorted by relevance
1234
| /external/arm-trusted-firmware/docs/security_advisories/ |
| D | security-advisory-tfv-8.rst | 6 | | Normal World SMC client to another |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact | Leakage of SMC return values from one normal world SMC |
28 into the firmware. However, for an SMC exception, the general purpose registers
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
57 In the presence of multiple normal world SMC clients, this behaviour might leak
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
[all …]
|
| D | security-advisory-tfv-1.rst | 5 | Title | Malformed Firmware Update SMC can result in copy of |
26 Generic Trusted Firmware (TF) BL1 code contains an SMC interface that is briefly
31 example, BL31 on AArch64 systems), the FWU SMC interface is replaced by the EL3
32 Runtime SMC interface. Platforms may choose how much of this FWU functionality
35 The BL1 FWU SMC handling code, currently only supported on AArch64, contains
51 validation checks while handling the ``FWU_SMC_IMAGE_COPY`` SMC. The SMC
93 blocks over multiple SMCs. ``block_size`` is an SMC argument and therefore
127 operation. Both ``block_size`` and ``image_size`` are SMC arguments. A very
|
| D | security-advisory-tfv-4.rst | 5 | Title | Malformed Firmware Update SMC can result in copy or |
57 The vulnerability resides in the BL1 FWU SMC handling code and it may be
71 The ``FWU_SMC_IMAGE_COPY`` SMC handler is designed to copy an image into secure
83 ``image_src`` is an SMC argument and therefore potentially controllable by an
93 The ``FWU_SMC_IMAGE_AUTH`` SMC handler is designed to authenticate an image
105 arguments through the SMC interface and injects high values whose sum overflows,
113 would need to be compromised in order to send a malformed FWU SMC that triggers
|
| D | security-advisory-tfv-6.rst | 58 its own branch predictor invalidation during context switch by issuing an SMC
66 implementing a specified `CVE-2017-5715`_ workaround SMC
68 is more efficient than calling an arbitrary SMC (for example ``PSCI_VERSION``).
76 This includes the time spent in test code conforming to the SMC Calling
|
| /external/arm-trusted-firmware/docs/getting_started/ |
| D | rt-svc-writers-guide.rst | 12 Call (SMC) instruction. These requests will follow the convention described in
13 the SMC Calling Convention PDD (`SMCCC`_). The `SMCCC`_ assigns function
14 identifiers to each SMC request and describes how arguments are passed and
17 SMC Functions are grouped together based on the implementor of the service, for
23 software. The common runtime services framework ensures that SMC Functions are
28 concepts and definitions described in the `SMCCC`_, in particular SMC Function
36 The SMC Function Identifier includes a OEN field. These values and their
39 with the SMC call type, which is either *Fast* or *Yielding*. Fast calls are
69 The SMC Function ID also indicates whether the call has followed the SMC32
76 specific handler for each SMC call, but it is expected that an individual
[all …]
|
| /external/arm-trusted-firmware/docs/components/ |
| D | firmware-update.rst | 52 #. Export a BL1 SMC interface to interoperate with other FWU images executing
128 BL1 SMC Interface
142 This SMC returns the number of SMCs supported by BL1.
155 This SMC returns the 128-bit `Universally Unique Identifier`_ for the
156 BL1 SMC service.
170 This SMC returns the current version of the BL1 SMC service.
188 This SMC passes execution control to an EL3 image described by the provided
190 this SMC for BL1 to pass execution control to BL31.
221 This SMC copies the secure image indicated by ``image_id`` from non-secure memory
224 provided in ``image_size`` when invoking this SMC for the first time for each
[all …]
|
| D | debugfs-design.rst | 76 SMC interface
79 The communication with the 9p layer in BL31 is made through an SMC conduit
80 (`SMC Calling Convention PDD`_), using a specific SiP Function Id. An NS shared
82 read operation. Refer to `ARM SiP Services`_ for a description of the SMC
111 The SMC interface is accessible from an NS environment, that is:
120 .. [#] `SMC Calling Convention PDD`_
|
| D | arm-sip-service.rst | 7 implementer or platform provider. They are accessed via ``SMC`` ("SMC calls")
8 instruction executed from Exception Levels below EL3. SMC calls for SiP
11 - Follow `SMC Calling Convention`_;
12 - Use SMC function IDs that fall in the SiP range, which are ``0xc2000000`` -
86 If the call is successful, the caller wouldn't observe the SMC returning.
94 The optional DebugFS interface is accessed through an SMC SiP service. Refer
|
| D | secure-partition-manager-design.rst | 47 - A range of synchronous exceptions (e.g. SMC function identifiers).
86 invoked through a SMC.
172 The `SMC Calling Convention`_ (*Arm DEN 0028B*) describes SMCs as a conduit for
188 ``MM_COMMUNICATE`` SMC will run to completion in the partition on a given CPU.
197 is passed as a parameter to the ``MM_COMMUNICATE`` SMC. The shared memory area
242 The `SMC Calling Convention`_ (*Arm DEN 0028B*) specification describes the SMC
252 from a Secure Partition as a SMC request to the SPM in EL3. Upon servicing the
253 SMC request, Trusted Firmware-A returns control directly to S-EL0 through an
259 The `SMC Calling Convention`_ (*Arm DEN 0028B*) specification describes the
260 32-bit and 64-bit calling conventions for the SMC and HVC conduits. The SVC
[all …]
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/MC/ARM/ |
| D | arm-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
16 @ SMC
18 smi #0xf @ SMI is old (ARMv6KZ) name for SMC
|
| D | arm-thumb-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
16 @ SMC
|
| /external/llvm/test/MC/ARM/ |
| D | arm-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
16 @ SMC
18 smi #0xf @ SMI is old (ARMv6KZ) name for SMC
|
| D | arm-thumb-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
16 @ SMC
|
| /external/u-boot/arch/arm/mach-omap2/ |
| D | lowlevel_init.S | 60 smc 0 @ SMC #0 to enter monitor mode
73 smc 0 @ SMC #0 to enter monitor mode
85 smc 0 @ SMC #0 to enter monitor mode
|
| /external/u-boot/doc/ |
| D | README.serial_multi | 7 At the moment, the ports must be split on a SMC and a SCC port on a
14 - SMC if keys not pressed (modem not enabled)
23 *) The console can be switched to SMC by any of the following commands:
|
| D | README.tee | 50 Lowest level of communication with OP-TEE builds on ARM SMC Calling
51 Convention (SMCCC) [2], which is the foundation for OP-TEE's SMC interface
55 OP-TEE SMC interface provides the basic functions required by SMCCC and some
|
| /external/arm-trusted-firmware/docs/design/ |
| D | interrupt-framework-design.rst | 773 secure interrupt during ``yielding`` SMC processing, save the registers that
796 The TSP issues an SMC with ``TSP_HANDLED_S_EL1_INTR`` as the function identifier to
800 upon receiving an SMC with ``TSP_HANDLED_S_EL1_INTR`` as the function identifier:
822 ``yielding`` SMC processing or by a higher priority EL3 interrupt during
830 ``yielding`` SMC in response to the ``TSP_FID_RESUME`` SMC from the normal world.
831 (See Section `Implication of preempted SMC on Non-Secure Software`_).
833 The non-secure interrupt triggered in Secure-EL1 during ``yielding`` SMC
849 i.e. **TEL3=0, CSS=0**. During ``yielding`` SMC processing, the IRQ
852 register context and issues an SMC with ``TSP_PREEMPTED`` as the function
853 identifier to signal preemption of TSP. The TSPD SMC handler,
[all …]
|
| /external/u-boot/arch/arm/mach-omap2/omap5/ |
| D | sec_entry_cpu1.S | 46 smc 0 @ SMC #0 to enter monitor mode
58 smc 0 @ SMC #0 to enter monitor mode
|
| /external/arm-trusted-firmware/docs/ |
| D | global_substitutions.txt | 41 .. |SMC| replace:: :term:`SMC`
|
| /external/u-boot/arch/arm/mach-mediatek/mt8518/ |
| D | lowlevel_init.S | 31 SMC #0
|
| /external/arm-trusted-firmware/docs/process/ |
| D | security.rst | 73 | |TFV-1| | Malformed Firmware Update SMC can result in copy of unexpectedly |
81 | |TFV-4| | Malformed Firmware Update SMC can result in copy or |
95 | | Normal World SMC client to another |
|
| /external/llvm/test/MC/Disassembler/ARM/ |
| D | arm-trustzone.txt | 6 # SMC
|
| D | arm-thumb-trustzone.txt | 6 # SMC
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/MC/Disassembler/ARM/ |
| D | arm-trustzone.txt | 6 # SMC
|
| D | arm-thumb-trustzone.txt | 6 # SMC
|
1234