From a23f07c09c9de7c3c87ce99aa38360f0c75222c6 Mon Sep 17 00:00:00 2001 From: Chen Gong Date: Thu, 15 Mar 2012 16:53:37 +0800 Subject: [PATCH] --- yaml --- r: 298057 b: refs/heads/master c: 6ef19ab7fa1535d35006535dba6c407dad2d845c h: refs/heads/master i: 298055: d8ef406f6f281909c80e76e86e73a6474700fe89 v: v3 --- [refs] | 2 +- trunk/Documentation/acpi/apei/einj.txt | 8 ++++++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 569b825bb758..c63e1cf295ce 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ee49089dc7d9fc78db51e18f4fba68e88edc49a4 +refs/heads/master: 6ef19ab7fa1535d35006535dba6c407dad2d845c diff --git a/trunk/Documentation/acpi/apei/einj.txt b/trunk/Documentation/acpi/apei/einj.txt index e7cc36397217..e20b6daaced4 100644 --- a/trunk/Documentation/acpi/apei/einj.txt +++ b/trunk/Documentation/acpi/apei/einj.txt @@ -53,6 +53,14 @@ directory apei/einj. The following files are provided. This file is used to set the second error parameter value. Effect of parameter depends on error_type specified. +- notrigger + The EINJ mechanism is a two step process. First inject the error, then + perform some actions to trigger it. Setting "notrigger" to 1 skips the + trigger phase, which *may* allow the user to cause the error in some other + context by a simple access to the cpu, memory location, or device that is + the target of the error injection. Whether this actually works depends + on what operations the BIOS actually includes in the trigger phase. + BIOS versions based in the ACPI 4.0 specification have limited options to control where the errors are injected. Your BIOS may support an extension (enabled with the param_extension=1 module parameter, or