From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [RFE] Add stacked registers to SAL records (resend)
Date: Fri, 05 Dec 2003 17:05:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107064399701180@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106870740330038@msgid-missing>
> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org
> [mailto:linux-ia64-owner@vger.kernel.org]On Behalf Of Bjorn Helgaas
> Sent: Friday, December 05, 2003 8:29 AM
> To: Keith Owens; linux-ia64@vger.kernel.org
> Subject: Re: [RFE] Add stacked registers to SAL records (resend)
>
>
> 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?
>
> I've always been puzzled about why the stacked registers aren't
> available after an INIT, so this proposal sounds incredibly useful
> to me. Much of the useful information, i.e., function arguments,
> is in the stacked registers and hence currently unavailable.
>
> As for getting it added to the spec, I don't really know the process.
> But I'll forward this to our people who deal with the spec. I think
> it would help to have an actual draft of a proposal.
>
> Tony Luck might have a good Intel contact, too.
I'm looking around for the right person to pass this to.
-Tony
next prev parent reply other threads:[~2003-12-05 17:05 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 [this message]
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-107064399701180@msgid-missing \
--to=tony.luck@intel.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 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.