All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Ross Lagerwall <ross.lagerwall@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v2] x86: Fixup IRQs when CPUs go down during shutdown
Date: Fri, 4 Dec 2015 10:46:41 +0000	[thread overview]
Message-ID: <56616F11.1080803@citrix.com> (raw)
In-Reply-To: <565F1C9202000078000BB534@prv-mh.provo.novell.com>

On 02/12/15 15:30, Jan Beulich wrote:
>>>> On 02.12.15 at 16:09, <ross.lagerwall@citrix.com> wrote:
>> On 12/02/2015 02:02 PM, Jan Beulich wrote:
>>>>>> On 02.12.15 at 14:46, <ross.lagerwall@citrix.com> wrote:
>>>> --- a/xen/arch/x86/smp.c
>>>> +++ b/xen/arch/x86/smp.c
>>>> @@ -286,6 +286,7 @@ void __stop_this_cpu(void)
>>>>
>>>>   static void stop_this_cpu(void *dummy)
>>>>   {
>>>> +    fixup_eoi();
>>>>       __stop_this_cpu();
>>> Is this really needed during shutdown?
>> Possibly not, but I think it's cleaner to do the same as what is used 
>> for CPU down.
> I'm not convinced. Andrew?

Suppose there is an oustanding line interrupt on the pending eoi stack. 
Without this fixup_eoi(), it could stay permanently attached to a cpu
which isn't processing anything further.

With the current use of smp_send_stop(), all cpus will end up in a state
where they can only be recovered with an #INIT, so I suppose it doesn't
actually matter.

Therefore, not performing redundant work is probably the best course of
action.

~Andrew

      reply	other threads:[~2015-12-04 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 13:46 [PATCH v2] x86: Fixup IRQs when CPUs go down during shutdown Ross Lagerwall
2015-12-02 13:53 ` Andrew Cooper
2015-12-02 14:02 ` Jan Beulich
2015-12-02 15:09   ` Ross Lagerwall
2015-12-02 15:30     ` Jan Beulich
2015-12-04 10:46       ` 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=56616F11.1080803@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ross.lagerwall@citrix.com \
    --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.