public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Matt D. Robinson" <yakker@alacritech.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: smp_send_stop() and disable_local_APIC()
Date: 04 May 2001 23:50:42 -0600	[thread overview]
Message-ID: <m1pudomjil.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3AF19A17.19C2741F@alacritech.com> <m1d79pnm2b.fsf@frodo.biederman.org> <3AF2E717.AF7936BD@alacritech.com>
In-Reply-To: "Matt D. Robinson"'s message of "Fri, 04 May 2001 10:29:59 -0700"

"Matt D. Robinson" <yakker@alacritech.com> writes:

> It's an SMP (and only when your system crashes on a CPU other
> than 0) problem.  I did some more checking of this to verify the
> specifics of the behavior.  Thanks for the sarcasm, though. :)

O.k.  That makes perfect sense then.  See below.

> All I wanted was clarification as to why it was added in the first
> place, and whether there was a better way around the scenario.
> I think Ingo added the code, but I never heard back from him.
> Thanks for the response.

Welcome.  Linux attempts to properly shutdown the apics when we are
shutting down, and part of that is returning the apics to the mode
they were before we got control.  To do that you need to disable every
cpu but the bootstrap processor, and return the bootstrap processor to
either virtual wire mode or pic_mode.  So of course it will be the
only cpu getting interrupts because we are in legacy mode.

I would say it probably makes sense to add an additional call.
smp_send_panic_stop that does exactly what you need instead of what is
needed on the normal shutdown path. 

Eric

      reply	other threads:[~2001-05-05 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-03 17:49 smp_send_stop() and disable_local_APIC() Matt D. Robinson
2001-05-04 15:58 ` Eric W. Biederman
2001-05-04 17:29   ` Matt D. Robinson
2001-05-05  5:50     ` Eric W. Biederman [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=m1pudomjil.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakker@alacritech.com \
    /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