All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: "Keir (Xen.org)" <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V5] x86/kexec: Change NMI and MCE handling on kexec path
Date: Thu, 13 Dec 2012 11:58:42 +0000	[thread overview]
Message-ID: <50C9C2F2.2010703@citrix.com> (raw)
In-Reply-To: <20121213115520.GB75286@ocelot.phlegethon.org>

On 13/12/12 11:55, Tim Deegan wrote:
> At 11:47 +0000 on 13 Dec (1355399235), Andrew Cooper wrote:
>>> nmi_shootdown_cpus() has a go, but I think it would have to do an atomic
>>> compare-exchange on crashing_cpu to actually be sure that only one CPU
>>> is crashing at a time.  If two CPUs try to lead crashes at the same
>>> time, it will deadlock here, with NMIs disabled on all CPUs.
>> kexec_common_shutdown() calls one_cpu_only() which gives the impression
>> that nmi_shootdown_cpus() can only be gotten to once.
> Right, I missed that.  So,
>
> Acked-by: Tim Deegan<tim@xen.org>
>
> You can tidy up entry.S or not, as you like.  There's no correctness
> issue with anything there, just things that could be neater if you were
> already updating the patch.
>
> Cheers,
>
> Tim.

I am just re spinning the patch for cli and the commit message.  Nothing 
major.

~Andrew

      reply	other threads:[~2012-12-13 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 11:35 [PATCH V5] x86/kexec: Change NMI and MCE handling on kexec path Andrew Cooper
2012-12-12 12:50 ` Jan Beulich
2012-12-12 15:33   ` Keir Fraser
2012-12-12 16:12     ` Jan Beulich
2012-12-13 10:59 ` Tim Deegan
2012-12-13 11:47   ` Andrew Cooper
2012-12-13 11:55     ` Tim Deegan
2012-12-13 11:58       ` Andrew Cooper [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=50C9C2F2.2010703@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.