From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFE] Add stacked registers to SAL records (resend)
Date: Mon, 08 Dec 2003 22:47:04 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107092374329608@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106870740330038@msgid-missing>
On Mon, 8 Dec 2003 11:41:32 -0700,
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>On Thursday 04 December 2003 5:59 pm, Keith Owens wrote:
>> SAL error records contain most registers in sal_processor_static_info,
>> but not the stacked registers. What is the process for adding another
>> GUID to the SAL specification to contain the stacked registers?
>
>One of our architecture guys pointed out that the stacked registers
>should still be intact at the OS_MCA and OS_INIT handoffs. They
>are unchanged in the PALE_CHECK and PALE_INIT exit state (I finally
>found this buried in the RSE description), and the OS_MCA and OS_INIT
>handoff state is defined to be the same for stacked registers.
>
>So I assume your proposal is to address the fact that we don't
>actually save the error records until after a reboot, and the
>stacked register contents are gone by then. Right?
Partly. Bu mainly because we need a new SAL error record section with
its own GUID and an agreed format.
You mentioned in another mail "Someone also raised the technical
question of whether the new format included enough information to
relate it to a particular processor, i.e., maybe it should include the
LID". We already have the lid, in sal_log_processor_info.
prev parent reply other threads:[~2003-12-08 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 7:08 [RFE] Add stacked registers to SAL records Keith Owens
2003-12-05 0:59 ` [RFE] Add stacked registers to SAL records (resend) Keith Owens
2003-12-05 16:28 ` Bjorn Helgaas
2003-12-05 17:05 ` Luck, Tony
2003-12-08 18:41 ` Bjorn Helgaas
2003-12-08 22:47 ` 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=marc-linux-ia64-107092374329608@msgid-missing \
--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