From: Russ Anderson <rja@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] New way of storing MCA/INIT logs
Date: Thu, 06 Mar 2008 17:52:08 +0000 [thread overview]
Message-ID: <20080306175208.GA12952@sgi.com> (raw)
In-Reply-To: <47CD8142.7050207@bull.net>
On Thu, Mar 06, 2008 at 02:14:48PM +0100, Zoltan Menyhart wrote:
> Luck, Tony wrote:
>
> Let's see this first:
>
> >Obviously entering polling
> >mode puts the responsibility onto SAL to keep track of all
> >the error reports
>
> Please have a look at the
> Figure 2-1. Itanium® Processor Family Firmware Machine Check Handling Model
> in the Error Handling Guide.
>
> This figure shows that the SAL (or the PAL) cannot see the platform
> originated CPEIs, nor the CPU HW originated CMCIs.
Figure 2-1 does show SAL passing up CPEI records to OS, too.
> When you call SAL_GET_STATE_INFO(), the SAL (and the PAL) will read out
> the error status from some HW registers.
>
> Therefore the SAL / PAL cannot store error reports.
See section 5.3.2 CMC and CPE Records
Each processor or physical platform could have multiple valid corrected
machine check or corrected platform error records. The maximum number of
these records present in a system depends on the SAL implementation and
the storage space available on the system. There is no requirement for
these records to be logged into NVM. The SAL may use an implementation
specific error record replacement algorithm for overflow situations. The
OS needs to make an explicit call to the SAL procedure SAL_CLEAR_STATE_INFO
to clear the CMC and CPE records in order to free up the memory resources
that may be used for future records.
5.4.1 Corrected Error Event Record
In response to a CMC/CPE condition, SAL builds and maintains the error
record for OS retrieval.
> Can the HW (platform or CPU) help to save error reports?
>
> A typical "error register set" - whatever it is - saves the first
> error and maintains a "cumulative error" status (usually reset
> by SAL_CLEAR_STATE_INFO()).
>
> CPEs / CMCs will be lost unless you (want to) "swallow" them
> quickly enough.
Yes, we want to handle the records as quickly as possible.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2008-03-06 17:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 17:05 [PATCH] New way of storing MCA/INIT logs Zoltan Menyhart
2008-03-05 0:23 ` Russ Anderson
2008-03-05 13:14 ` Zoltan Menyhart
2008-03-05 16:59 ` Luck, Tony
2008-03-05 18:56 ` Russ Anderson
2008-03-05 23:38 ` Keith Owens
2008-03-06 10:24 ` Zoltan Menyhart
2008-03-06 13:14 ` Zoltan Menyhart
2008-03-06 17:09 ` Luck, Tony
2008-03-06 17:29 ` Zoltan Menyhart
2008-03-06 17:52 ` Russ Anderson [this message]
2008-03-06 21:56 ` Luck, Tony
2008-03-06 22:13 ` Russ Anderson
2008-03-07 12:02 ` Zoltan Menyhart
2008-03-07 16:55 ` Russ Anderson
2008-03-10 9:36 ` Zoltan Menyhart
2008-03-10 20:36 ` Russ Anderson
2008-03-10 21:10 ` Russ Anderson
2008-03-11 14:07 ` Zoltan Menyhart
2008-03-11 14:32 ` Robin Holt
2008-03-11 21:22 ` Russ Anderson
2008-03-12 1:08 ` Keith Owens
2008-03-12 7:42 ` Zoltan Menyhart
2008-04-01 15:18 ` [PATCH] New way of storing MCA/INIT logs - take 2 Zoltan Menyhart
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=20080306175208.GA12952@sgi.com \
--to=rja@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox