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

I put this comment in arch/ia64/kernel/mca_asm.S, where we switch to
the MCA/INIT stack.  The code runs fine without wiring
IA64_KR_CURRENT_STACK and IA64_TR_CURRENT_STACK.  Is that coincidence
or do the extra registers really need to be updated?  The MCA/INIT
stacks are initialized early in boot, they are in region 7.

Remember that the MCA/INIT handlers run with interrupts disabled.

ia64_set_kernel_registers:
        add temp3=MCA_SP_OFFSET, r3
        add temp4=MCA_SOS_OFFSET+IA64_SAL_OS_STATE_OS_GP_OFFSET, r3
        mov b0=r2               // save return address
        GET_IA64_MCA_DATA(temp1)
        ;;
        add temp4=temp4, temp1  // &struct ia64_sal_os_state.os_gp
        add r12=temp1, temp3    // kernel stack pointer on MCA/INIT stack
        add r13=temp1, r3       // set current to start of MCA/INIT stack
        ;;
        ld8 r1=[temp4]          // OS GP from SAL OS state
        ;;
        DATA_PA_TO_VA(r1,temp1)
        DATA_PA_TO_VA(r12,temp2)
        DATA_PA_TO_VA(r13,temp3)
        ;;
        mov IA64_KR(CURRENT)=r13

        // FIXME: do I need to wire IA64_KR_CURRENT_STACK and IA64_TR_CURRENT_STACK?

        br.sptk b0



             reply	other threads:[~2005-09-21  1:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21  1:12 Keith Owens [this message]
2005-09-21 17:47 ` MCA/INIT: need to wire CURRENT_STACK? 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

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=16451.1127265127@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