Linux IA64 platform development
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Make MCA stack look like a normal kernel stack
Date: Thu, 10 Feb 2005 02:26:37 +0000	[thread overview]
Message-ID: <16906.50781.867221.701264@napali.hpl.hp.com> (raw)
In-Reply-To: <10372.1107999173@kao2.melbourne.sgi.com>

>>>>> On Thu, 10 Feb 2005 12:32:53 +1100, Keith Owens <kaos@sgi.com> said:

  Keith> I have a long term aim to make the MCA and INIT stacks look
  Keith> like normal process stacks

That would indeed simplify life for the unwinder a bit, though it's
not strictly needed.  Alternatively, it might be possible to define
the proc_state_dump area as yet another special frame.  I would prefer
if this can be avoided, though.

  Keith> * MCA stack in struct ia64_mca_cpu looks like a normal kernel stack,
  Keith> * except that the rse_stack and proc_state_dump are stored at the
  Keith> * top of the MCA stack.  All entries are 16 byte aligned.
  Keith> *
  Keith> *      +---------------------------+
  Keith> *      |       RSE stack frame     |
  Keith> *      +---------------------------+
  Keith> *      |       proc_state_dump     |
  Keith> *      +---------------------------+
  Keith> *      |           pt_regs         |
  Keith> *      +---------------------------+
  Keith> *      |    16 byte scratch area   |
  Keith> *      +---------------------------+ <-- SP at start of C MCA handler
  Keith> *      |           .....           |
  Keith> *      +---------------------------+
  Keith> *      |    RBS for MCA handler    |
  Keith> *      +---------------------------+
  Keith> *      | struct task, not used yet |
  Keith> *      +---------------------------+ <-- Bottom of MCA stack

Hmmh, I don't understand why "RSE stack frame" is at the
highest-address-end of the stack.  Why not make it part of the RBS, as
is normally done?

Also, I'd hope that proc_state_dump isn't needed as part of the
task-structure: we should be able to store part of its contents in
pt_regs and the rest should be loaded into the preserved registers
before calling the first C routine.  No?

	--david

  reply	other threads:[~2005-02-10  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10  1:32 Make MCA stack look like a normal kernel stack Keith Owens
2005-02-10  2:26 ` David Mosberger [this message]
2005-02-10  2:47 ` Keith Owens
2005-02-10  5:38 ` David Mosberger

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=16906.50781.867221.701264@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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