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: [patch] Resched skip_rbs_switch to run 4 cycles faster on McKinley-type cores.
Date: Fri, 28 Jan 2005 03:04:35 +0000	[thread overview]
Message-ID: <13236.1106881475@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <200501190500.j0J505jY002441@napali.hpl.hp.com>

On Thu, 27 Jan 2005 18:08:18 -0800, 
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>>>>>> On Thu, 20 Jan 2005 21:26:18 +1100, Keith Owens <kaos@sgi.com> said:
>
>  Keith> Unwinding across firmware is not an issue here, we have two
>  Keith> views of the MCA/INIT context.  One view is "how to return to
>  Keith> SAL?", that data is stored outside the stack.  The other view
>  Keith> is "what was the cpu doing when the event occurred?".  It is
>  Keith> the latter that I am working on.
>
>How is this different from the "unw_init_from_interruption" call that
>we're doing in mca.c:init_handler_platform()?

That only works for the INIT call which uses the current bspstore, MCA
uses its own bspstore.  The kernel unwinder is not set up to switch
bspstore between two kernel stacks, only between kernel and user space.
The INIT call will change to its own bspstore once we use the separate
INIT and MCA stacks for each cpu.


  parent reply	other threads:[~2005-01-28  3:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  5:00 [patch] Resched skip_rbs_switch to run 4 cycles faster on McKinley-type cores David Mosberger
2005-01-19 22:25 ` Keith Owens
2005-01-20  6:50 ` David Mosberger
2005-01-20 10:26 ` Keith Owens
2005-01-20 17:01 ` David Mosberger
2005-01-28  2:08 ` David Mosberger
2005-01-28  3:04 ` Keith Owens [this message]
2005-01-28  5:22 ` 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=13236.1106881475@kao2.melbourne.sgi.com \
    --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