This actually works depends on what operations the BIOS actuallyīIOS versions based on the ACPI 4.0 specification have limited options Location, or device that is the target of the error injection. To 1 skips the trigger phase, which may allow the user to cause theĮrror in some other context by a simple access to the CPU, memory First inject theĮrror, then perform some actions to trigger it. The error injection mechanism is a two-step process. Used when the 0x4 bit is set in “flags” to specify target PCIe device Used when the 0x1 bit is set in “flags” to specify the APIC id Linux requires page or narrower granularity, say, 0xfffffffffffff000. Related type, then param2 should be a physical memory address mask. For example, ifĮrror type is memory related type, the param1 should be a valid Its effectĭepends on the error type specified in error_type.
This file is used to set the first error parameter value. Injection specifies just one bit set, and param1 is multiplexed. If set to zero, legacy behavior is mimicked where the type of PCIe (seg,bus,dev,fn) valid (see param4 below). Memory address and mask valid (param1 and param2). Processor APIC field valid (see param3 below). SET_ERROR_TYPE_WITH_ADDRESS data structure: Value is a bitmask as specified in ACPI5.0 spec for the Of param are valid and should be used by the firmware during Present for kernel versions 3.13 and above. Write should be the last step when injecting errors. Sure you have specified all necessary error parameters, i.e. Write any integer to this file to trigger the error injection. Possible error typesĪre defined in the file available_error_type above. Set the value of the error type being injected. The format of the file contents are as above, except present are only This file shows which error types are supported: The EINJ user interface is in /apei/einj.
0 kommentar(er)
