acpi/apei/einj.rst

1 .. SPDX-License-Identifier: GPL-2.0
15 which shows that the BIOS is exposing an EINJ table - it is the
43 - available_error_type
51   0x00000002        Processor Uncorrectable non-fatal
54   0x00000010        Memory Uncorrectable non-fatal
57   0x00000080        PCI Express Uncorrectable non-fatal
60   0x00000400        Platform Uncorrectable non-fatal
67 - error_type
72 - error_inject
74   Write any integer to this file to trigger the error injection. Make
78 - flags
88       Memory address and mask valid (param1 and param2).
95 - param1
100   physical memory address. [Unless "flag" is set - see above]
102 - param2
105   related type, then param2 should be a physical memory address mask.
108 - param3
112 - param4
115 - notrigger
117   The error injection mechanism is a two-step process. First inject the
118   error, then perform some actions to trigger it. Setting "notrigger"
119   to 1 skips the trigger phase, which *may* allow the user to cause the
123   includes in the trigger phase.
129 - einj_types:
134 - $dport_dev/einj_inject:
146 command line einj.param_extension=1). This allows the address and mask
151 the target of the injection. For processor-related errors (type 0x1, 0x2
161 For memory errors (type 0x8, 0x10 and 0x20) the address is set using
167 	+-------------------------------------------------+
169 	+-------------------------------------------------+
174 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected.
177 the vendor-specific extension to tell that they are running on a BIOS
189   0x00000002	Processor Uncorrectable non-fatal
191   0x00000010	Memory Uncorrectable non-fatal
192   # echo 0x12345000 > param1		# Set memory address for injection
193   # echo 0xfffffffffffff000 > param2		# Mask - anywhere in this page
204 …el#0_DIMM#0 (channel:0 slot:0 page:0x12345 offset:0x0 grain:32 syndrome:0x0 -  area:DRAM err_code:…
213 	0x00010000  CXL.mem Protocol Uncorrectable non-fatal
223 trigger that will inject the error on the next write to the target
224 address. But the h/w prevents any software outside of an SGX enclave
228   1) Determine physical address of enclave page
230      the injection address, but will not actually inject)
232   4) Store data to the virtual address matching physical address from step 1
233   5) Execute CLFLUSH for that virtual address
235   7) Read from the virtual address. This will trigger the error