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: Re: MCA/INIT: need to wire CURRENT_STACK?
Date: Wed, 21 Sep 2005 23:21:14 +0000	[thread overview]
Message-ID: <14725.1127344874@ocs3.ocs.com.au> (raw)
In-Reply-To: <16451.1127265127@ocs3.ocs.com.au>

On Wed, 21 Sep 2005 16:09:49 -0700, 
David Mosberger-Tang <David.Mosberger@acm.org> wrote:
>On 9/21/05, Keith Owens <kaos@sgi.com> wrote:
>> On Wed, 21 Sep 2005 11:12:58 -0700,
>
>> The virtual mode handlers are entered with psr.ic=1 and psr.i=0.
>
>I'm not sure what you mean by virtual mode handlers,

The C code that starts with ia64_mca_handler and ia64_init_handler.
mca_asm.S is entered in physical mode with psr.ic=0, it switches to
virtual with psr.ic=1 and psr.i=0 before calling the handlers.

>but execution in
>the IVT starts with PSR.IC=0.

Right, so the real question is - is there any path that causes an
interrupt before the virtual mode handlers have accessed their stacks
and the required DTC has been created?  Alternatively can the DTC for
the MCA/INIT stacks be lost once the handlers have started running?

Given the uncertainty and the fact the the TLB error recovery in
mca_asm.S assumes that CURRENT_STACK is defined, I need to wire
CURRENT_STACK around the C code handlers.  Patch coming soon.

BTW David, are you aware that your mailer is using quoted printable,
even for plain text messages?  All the '=' signs come out as '='.


      parent reply	other threads:[~2005-09-21 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21  1:12 MCA/INIT: need to wire CURRENT_STACK? Keith Owens
2005-09-21 17:47 ` Luck, Tony
2005-09-21 18:12 ` David Mosberger-Tang
2005-09-21 22:58 ` Keith Owens
2005-09-21 23:09 ` David Mosberger-Tang
2005-09-21 23:21 ` 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=14725.1127344874@ocs3.ocs.com.au \
    --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