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
39 - available_error_type
47   0x00000002        Processor Uncorrectable non-fatal
50   0x00000010        Memory Uncorrectable non-fatal
53   0x00000080        PCI Express Uncorrectable non-fatal
56   0x00000400        Platform Uncorrectable non-fatal
63 - error_type
68 - error_inject
70   Write any integer to this file to trigger the error injection. Make
74 - flags
84       Memory address and mask valid (param1 and param2).
91 - param1
96   physical memory address. [Unless "flag" is set - see above]
98 - param2
101   related type, then param2 should be a physical memory address mask.
104 - param3
108 - param4
111 - notrigger
113   The error injection mechanism is a two-step process. First inject the
114   error, then perform some actions to trigger it. Setting "notrigger"
115   to 1 skips the trigger phase, which *may* allow the user to cause the
119   includes in the trigger phase.
124 command line einj.param_extension=1). This allows the address and mask
129 the target of the injection. For processor-related errors (type 0x1, 0x2
139 For memory errors (type 0x8, 0x10 and 0x20) the address is set using
145 	+-------------------------------------------------+
147 	+-------------------------------------------------+
152 An ACPI 5.0 BIOS may also allow vendor-specific errors to be injected.
155 the vendor-specific extension to tell that they are running on a BIOS
167   0x00000002	Processor Uncorrectable non-fatal
169   0x00000010	Memory Uncorrectable non-fatal
170   # echo 0x12345000 > param1		# Set memory address for injection
171   # echo 0xfffffffffffff000 > param2		# Mask - anywhere in this page
182 …el#0_DIMM#0 (channel:0 slot:0 page:0x12345 offset:0x0 grain:32 syndrome:0x0 -  area:DRAM err_code:…
189 trigger that will inject the error on the next write to the target
190 address. But the h/w prevents any software outside of an SGX enclave
194   1) Determine physical address of enclave page
196      the injection address, but will not actually inject)
198   4) Store data to the virtual address matching physical address from step 1
199   5) Execute CLFLUSH for that virtual address
201   7) Read from the virtual address. This will trigger the error