From: Chen Gong <gong.chen@linux.intel.com>
To: tony.luck@intel.com, bp@alien8.de
Cc: linux-acpi@vger.kernel.org, Chen Gong <gong.chen@linux.intel.com>
Subject: [PATCH 2/2 V2] ACPI/APEI: Update einj documentation for param1/param2
Date: Mon, 20 May 2013 03:20:33 -0400 [thread overview]
Message-ID: <1369034433-13666-3-git-send-email-gong.chen@linux.intel.com> (raw)
In-Reply-To: <1369034433-13666-1-git-send-email-gong.chen@linux.intel.com>
To ensure EINJ working well when injecting errors via EINJ
table, add some attentions for param1/param2.
Signed-off-by: Chen Gong <gong.chen@linux.intel.com>
---
Documentation/acpi/apei/einj.txt | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/Documentation/acpi/apei/einj.txt b/Documentation/acpi/apei/einj.txt
index e20b6da..3b08e62 100644
--- a/Documentation/acpi/apei/einj.txt
+++ b/Documentation/acpi/apei/einj.txt
@@ -47,11 +47,15 @@ directory apei/einj. The following files are provided.
- param1
This file is used to set the first error parameter value. Effect of
- parameter depends on error_type specified.
+ parameter depends on error_type specified. For example, if error
+ type is memory related type, the param1 should be a valid physical
+ memory address.
- param2
This file is used to set the second error parameter value. Effect of
- parameter depends on error_type specified.
+ parameter depends on error_type specified. For example, if error
+ type is memory related type, the param2 should be a valid physical
+ memory address mask, say, 0xfffffffffffff000.
- notrigger
The EINJ mechanism is a two step process. First inject the error, then
--
1.7.10.4
prev parent reply other threads:[~2013-05-20 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 7:20 Parameter check for EINJ error injection - V2 Chen Gong
2013-05-20 7:20 ` [PATCH 1/2 V2] ACPI/APEI: Add parameter check before error injection Chen Gong
2013-05-21 20:19 ` Luck, Tony
2013-05-22 6:10 ` Chen Gong
2013-05-22 10:33 ` Borislav Petkov
2013-05-20 7:20 ` Chen Gong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1369034433-13666-3-git-send-email-gong.chen@linux.intel.com \
--to=gong.chen@linux.intel.com \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.