diff options
| author | Chen Gong <gong.chen@linux.intel.com> | 2012-03-15 16:53:37 +0800 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2012-03-30 03:30:19 -0400 |
| commit | 6ef19ab7fa1535d35006535dba6c407dad2d845c (patch) | |
| tree | ebc8d0a9341ac4cfd5970b0eacf45e548a31a0eb /Documentation | |
| parent | ee49089dc7d9fc78db51e18f4fba68e88edc49a4 (diff) | |
| download | linux-3.10-6ef19ab7fa1535d35006535dba6c407dad2d845c.tar.gz linux-3.10-6ef19ab7fa1535d35006535dba6c407dad2d845c.tar.bz2 linux-3.10-6ef19ab7fa1535d35006535dba6c407dad2d845c.zip | |
Update documentation for parameter *notrigger* in einj.txt
Add description of parameter notrigger in the einj.txt.
One can utilize this new parameter to do some SRAR injection
test. Pay attention, the operation is highly depended on the
BIOS implementation. If no proper BIOS supports it, even if
enabling this parameter, expected result will not happen.
v2:
Update the documentation suggested by Tony
Suggested-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Chen Gong <gong.chen@linux.intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/acpi/apei/einj.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/acpi/apei/einj.txt b/Documentation/acpi/apei/einj.txt index e7cc3639721..e20b6daaced 100644 --- a/Documentation/acpi/apei/einj.txt +++ b/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 |