From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] Change the effect of SAL_{GET,CLEAR}_STATE_INFO for MCA/INIT records
Date: Tue, 14 Dec 2004 01:26:23 +0000 [thread overview]
Message-ID: <8877.1102987583@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <12433.1102594994@ocs3.ocs.com.au>
On Mon, 13 Dec 2004 17:00:21 -0800,
"Luck, Tony" <tony.luck@intel.com> wrote:
>>The OS MCA and, to a lesser extent, the INIT handlers have to decide if
>>the MCA/INIT is recoverable or not. To make that decision, the OS
>>handlers need the current MCA/INIT record because that is the only
>>record that contains the data needed to make the decision. If there
>>are multiple MCA/INIT records stored for a cpu then SAL_GET_STATE_INFO
>>returns the top record every time, resulting in bad data and invalid
>>decisions about recovery.
>
>Isn't all the information on whether the current MCA/INIT event is
>recoverable encoded in the processor state parameter ... which is
>passed to the OS by SAL in r18. What do you need that requires that
>you get at the error record?
The PSP bits only tell us that the event might be recoverable. We need
more data from the MCA record to make the final decision.
prev parent reply other threads:[~2004-12-14 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 12:23 [RFC] Change the effect of SAL_{GET,CLEAR}_STATE_INFO for MCA/INIT records Keith Owens
2004-12-10 2:51 ` [RFC] Change the effect of SAL_{GET,CLEAR}_STATE_INFO for MCA/INIT Hidetoshi Seto
2004-12-13 3:54 ` [RFC] Change the effect of SAL_{GET,CLEAR}_STATE_INFO for MCA/INIT records Keith Owens
2004-12-14 1:00 ` Luck, Tony
2004-12-14 1:26 ` Keith Owens [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=8877.1102987583@kao2.melbourne.sgi.com \
--to=kaos@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