All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Sending cpu 0 back to SAL slave loop
Date: Sun, 08 Oct 2006 07:37:04 +0000	[thread overview]
Message-ID: <8352.1160293024@ocs3.ocs.com.au> (raw)
In-Reply-To: <20061006203909.GA6500@sgi.com>

Matthew Wilcox (on Fri, 6 Oct 2006 14:44:43 -0600) wrote:
>On Fri, Oct 06, 2006 at 03:39:10PM -0500, Jack Steiner wrote:
>> For kexec, it is ESSENTIAL that all cpus except for the one doing
>> the kexec be returned to the SAL slave loop. If this is not done, our
>> chipset will misdirect IO interrupts on the newly exec'ed kernel.
>
>Could you do an IPI call to have CPU 0 do the kexec and have the CPU
>that sent the IPI fall into the SAL slave loop instead?

An IPI call will not work for MCA or INIT.  Both of those drive all
cpus into a state which has disabled interrupts.


  parent reply	other threads:[~2006-10-08  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 20:39 Sending cpu 0 back to SAL slave loop Jack Steiner
2006-10-06 20:44 ` Matthew Wilcox
2006-10-07  2:16 ` Jack Steiner
2006-10-08  5:40 ` Zou, Nanhai
2006-10-08  7:37 ` Keith Owens [this message]
2006-10-09 15:09 ` Jack Steiner

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=8352.1160293024@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.