All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Huang Ying <ying.huang@intel.com>
Cc: lenb@kernel.org, ak@linux.intel.com,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5/5] ACPI, APEI, Document for APEI
Date: Wed, 6 Jan 2010 08:16:09 +0100	[thread overview]
Message-ID: <20100106071609.GA1648@ucw.cz> (raw)
In-Reply-To: <20100106071431.GB1494@ucw.cz>


> > +The user interface of EINJ is in debug file system, under the
> > +directory apei/einj. The following files are provided.
> > +
> > +- available_error_type
> > +  Read this file will return the error injection capability of the
> > +  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.

Strange interface. Why not simply pass single integer -- the bit mask?
Bit meanings are not going to change, anyway.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-01-06  7:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  6:12 [PATCH -v3 0/5] ACPI, APEI, APEI basic support Huang Ying
2009-12-28  6:12 ` [PATCH 1/5] ACPI, IO memory pre-mapping and atomic accessing Huang Ying
2009-12-28  6:12   ` [PATCH 2/5] ACPI, APEI, APEI supporting infrastructure Huang Ying
2009-12-28  6:12     ` [PATCH 3/5] ACPI, APEI, HEST table parsing Huang Ying
2009-12-28  6:12       ` [PATCH 4/5] ACPI, APEI, EINJ support Huang Ying
2009-12-28  6:12         ` [PATCH 5/5] ACPI, APEI, Document for APEI Huang Ying
2010-01-06  7:14           ` Pavel Machek
2010-01-06  7:16             ` Pavel Machek [this message]
2010-01-06  7:21               ` Huang Ying
2010-01-07  7:12                 ` Pavel Machek
2010-01-07  7:26                   ` Huang Ying
2010-01-07  7:34                     ` Pavel Machek
2010-01-06  7:08         ` [PATCH 4/5] ACPI, APEI, EINJ support Pavel Machek
2010-01-06  7:16           ` Huang Ying
2010-01-07  7:12             ` Pavel Machek
2009-12-31  1:14     ` git-apply --whitespace (Re: [PATCH 2/5] ACPI, APEI, APEI supporting infrastructure) Len Brown
2009-12-31  1:19       ` Huang Ying
2009-12-31  1:19 ` [PATCH -v3 0/5] ACPI, APEI, APEI basic support Len Brown

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=20100106071609.GA1648@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=ak@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@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.