public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [RFE] Add stacked registers to SAL records (resend)
Date: Fri, 05 Dec 2003 00:59:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-107058596016407@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106870740330038@msgid-missing>

Originally sent November 13 with no response, try again.

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?

Layout:

  number of stacked registers in this record
  cfm for frame at the time of failure
  stacked registers, ending with the cfm.sof registers

This GUID would be optional, if a particular SAL implementation did not
produce it then that platform would not have stacked registers printed
via salinfo.


  reply	other threads:[~2003-12-05  0:59 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 ` Keith Owens [this message]
2003-12-05 16:28 ` [RFE] Add stacked registers to SAL records (resend) Bjorn Helgaas
2003-12-05 17:05 ` Luck, Tony
2003-12-08 18:41 ` Bjorn Helgaas
2003-12-08 22:47 ` Keith Owens

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-107058596016407@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