[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1274238402.24034.12.camel@yhuang-dev.sh.intel.com>
Date: Wed, 19 May 2010 11:06:42 +0800
From: Huang Ying <ying.huang@...el.com>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: "lenb@...nel.org" <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"andi@...stfloor.org" <andi@...stfloor.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH -v5 05/14] ACPI, APEI, Document for APEI
Hi, Randy,
On Wed, 2010-05-19 at 05:51 +0800, Randy Dunlap wrote:
> Huang Ying wrote:
> > Add document for APEI, including kernel parameters and EINJ debug file
> > sytem interface.
> >
> > Signed-off-by: Huang Ying <ying.huang@...el.com>
> > Signed-off-by: Andi Kleen <ak@...ux.intel.com>
> > ---
> > Documentation/acpi/apei/einj.txt | 49 ++++++++++++++++++++++++++++++++++++
> > Documentation/kernel-parameters.txt | 5 +++
> > 2 files changed, 54 insertions(+)
> > create mode 100644 Documentation/acpi/apei/einj.txt
> >
> > --- /dev/null
> > +++ b/Documentation/acpi/apei/einj.txt
> > @@ -0,0 +1,49 @@
> > + APEI Error INJection
> > + ~~~~~~~~~~~~~~~~~~~~
> > +
> > +EINJ provides a hardware error injection mechanism, it is very useful
>
> ; [or . + new sentence]
>
> > +for debugging and testing of other APEI and RAS features.
> > +
> > +To use EINJ, make the following is enabled in your kernel
>
> make sure the following are enabled
>
> > +configuration:
> > +
> > +CONFIG_DEBUG_FS
> > +CONFIG_ACPI_APEI
> > +CONFIG_ACPI_APEI_EINJ
> > +
> > +The user interface of EINJ is in debug file system, under the
>
> is the debug file system,
> [or "is in the debug file system"]
>
> > +directory apei/einj. The following files are provided.
> > +
> > +- available_error_type
> > + Read this file will return the error injection capability of the
>
> Reading this file returns ...
>
> > + platform, that is, which error types are supported. The error type
> > + definition is as follow, the left field is the error type value, the
> > + right field is error description.
> > +
> > + 0x00000001 Processor Correctable
> > + 0x00000002 Processor Uncorrectable non-fatal
> > + 0x00000004 Processor Uncorrectable fatal
> > + 0x00000008 Memory Correctable
> > + 0x00000010 Memory Uncorrectable non-fatal
> > + 0x00000020 Memory Uncorrectable fatal
> > + 0x00000040 PCI Express Correctable
> > + 0x00000080 PCI Express Uncorrectable fatal
> > + 0x00000100 PCI Express Uncorrectable non-fatal
> > + 0x00000200 Platform Correctable
> > + 0x00000400 Platform Uncorrectable non-fatal
> > + 0x00000800 Platform Uncorrectable fatal
> > +
> > + The format of file contents are as above, except there are only the
> > + available error type lines.
> > +
> > +- error_type
> > + This file is used to set the error type value. The error type value
> > + is defined in "available_error_type" description.
> > +
> > +- error_inject
> > + Write any integer to this file to trigger the error
> > + injection. Before this, please specify all necessary error
> > + parameters.
> > +
> > +For more information about EINJ, please refer to ACPI specification
> > +version 4.0, section 17.5.
> > --- a/Documentation/kernel-parameters.txt
> > +++ b/Documentation/kernel-parameters.txt
> > @@ -843,6 +843,11 @@ and is between 256 and 4096 characters.
> > hd= [EIDE] (E)IDE hard drive subsystem geometry
> > Format: <cyl>,<head>,<sect>
> >
> > + hest_disable [ACPI]
> > + Disable Hardware Error Source Table (HEST) support,
>
> s/,/;/
>
> > + corresponding firmware-first mode error processing
> > + logic will be disabled.
> > +
> > highmem=nn[KMG] [KNL,BOOT] forces the highmem zone to have an exact
> > size of <nn>. This works even on boxes that have no
> > highmem otherwise. This also works to reduce highmem
Thanks, will fix theses. Sorry for my poor English.
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists