From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: INIT handler modification
Date: Sat, 08 Jan 2005 01:26:49 +0000 [thread overview]
Message-ID: <4479.1105147609@ocs3.ocs.com.au> (raw)
In-Reply-To: <41DE990B.702@Ext.Bull.Net>
On Fri, 07 Jan 2005 15:13:31 +0100,
Francois Wellenreiter <Francois.Wellenreiter@Ext.Bull.Net> wrote:
>Here is the main point, the present code of INIT handler for slave CPUs
>is reduced
>to (file arch/ia64/kernel/mca_asm.S) :
>______________________________
>
>GLOBAL_ENTRY(ia64_slave_init_handler)
>1: br.sptk 1b
>END(ia64_slave_init_handler)
>______________________________
The limitations on slave INIT and MCA handlers are mainly due to the
lack of kernel stacks to handle these events. Russ Anderson (SGI) is
working on patches that add per cpu stacks for MCA and INIT. Once
those patches are in the base kernel, we will be changing the INIT and
MCA slave handlers to use the multiple stacks. That will give us real
processing for the slave events.
next prev parent reply other threads:[~2005-01-08 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 14:13 INIT handler modification Francois Wellenreiter
2005-01-07 17:51 ` Bjorn Helgaas
2005-01-07 23:57 ` Luck, Tony
2005-01-08 1:26 ` Keith Owens [this message]
2005-01-09 17:21 ` Russ Anderson
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=4479.1105147609@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