From: Don Zickus <dzickus@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
andi@firstfloor.org, torvalds@linux-foundation.org,
peterz@infradead.org, robert.richter@amd.com, tglx@linutronix.de,
mingo@elte.hu, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/debug] x86, reboot: Use NMI instead of REBOOT_VECTOR to stop cpus
Date: Thu, 22 Dec 2011 15:16:47 -0500 [thread overview]
Message-ID: <20111222201642.GZ5650@redhat.com> (raw)
In-Reply-To: <CAE9FiQUW5tf5-Fbn0a_8s58P+7rXbG6iWPaDeHOuhxw4TZE+hQ@mail.gmail.com>
On Wed, Dec 21, 2011 at 10:24:53AM -0800, Yinghai Lu wrote:
> On Wed, Dec 21, 2011 at 6:59 AM, Don Zickus <dzickus@redhat.com> wrote:
> > On Tue, Dec 20, 2011 at 02:38:39PM -0800, Yinghai Lu wrote:
> >> > @@ -230,7 +285,7 @@ struct smp_ops smp_ops = {
> >> > .smp_prepare_cpus = native_smp_prepare_cpus,
> >> > .smp_cpus_done = native_smp_cpus_done,
> >> >
> >> > - .stop_other_cpus = native_stop_other_cpus,
> >> > + .stop_other_cpus = native_nmi_stop_other_cpus,
> >> > .smp_send_reschedule = native_smp_send_reschedule,
> >> >
> >> > .cpu_up = native_cpu_up,
> >>
> >> this broke kexec on our intel nehalem, westmere and sandbridge platforms.
> >> system get reset while try to kexec second kernel.
> >
> >
> > Hmm. Ok. Does the reboot path work correctly?
>
> Yes.
>
> > Vivek showed me that the
> > kexec and reboot paths do the same shutdowns. Perhaps the second kernel
> > has trouble dealing with cpus spinning in an NMI context and can't
> > properly reset them.
>
> not sure.
> when use nonmi_ipi in first kernel, it will work well.
Ok. I tried taking the cpus out of NMI context and putting them into irq
context with irq_work_queue() but that didn't seem to work. It seems to
be hanging in the new kernel somewhere. I'll have to wait until I get
back into the office next year to debug with early_printk and a vga
console.
Cheers,
Don
next prev parent reply other threads:[~2011-12-22 20:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 19:14 [v2 PATCH 0/3] Use NMI to stop cpus Don Zickus
2011-10-13 19:14 ` [v2 PATCH 1/3] x86, reboot: Use NMI instead of REBOOT_VECTOR " Don Zickus
2011-12-05 13:21 ` [tip:x86/debug] " tip-bot for Don Zickus
2011-12-20 22:38 ` Yinghai Lu
2011-12-21 14:59 ` Don Zickus
2011-12-21 18:24 ` Yinghai Lu
2011-12-22 20:16 ` Don Zickus [this message]
2012-01-05 18:17 ` Don Zickus
2012-01-05 21:44 ` Yinghai Lu
2011-10-13 19:14 ` [v2 PATCH 2/3] x86, NMI: Add NMI IPI selftest Don Zickus
2011-12-05 13:22 ` [tip:x86/debug] " tip-bot for Don Zickus
2011-12-06 9:06 ` Ingo Molnar
2011-12-06 18:08 ` Don Zickus
2011-12-06 20:01 ` Ingo Molnar
2011-12-06 20:25 ` [tip:x86/debug] x86, NMI: NMI-selftest should handle the UP case properly tip-bot for Don Zickus
2011-12-07 11:06 ` [patch] x86, NMI: add to_cpumask() to silence compile warning Dan Carpenter
2011-12-07 14:59 ` Don Zickus
2011-12-07 21:12 ` Don Zickus
2011-10-13 19:14 ` [v2 PATCH 3/3] x86, NMI: knob to disable using NMI IPIs to stop cpus Don Zickus
2011-12-05 13:23 ` [tip:x86/debug] x86, NMI: Add " tip-bot for Don Zickus
2011-11-08 19:25 ` [v2 PATCH 0/3] Use NMI " Don Zickus
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=20111222201642.GZ5650@redhat.com \
--to=dzickus@redhat.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).