From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: linux-kernel@vger.kernel.org, toshi.kani@hp.com, x86@kernel.org,
mingo@redhat.com, hpa@zytor.com, xen-devel@lists.xenproject.org,
tglx@linutronix.de
Subject: Re: [Xen-devel] [PATCH v7] x86: initialize secondary CPU only if master CPU will wait for it
Date: Tue, 24 Jun 2014 13:25:25 -0400 [thread overview]
Message-ID: <53A9B485.9000303@oracle.com> (raw)
In-Reply-To: <1403266991-12233-1-git-send-email-imammedo@redhat.com>
On 06/20/2014 08:23 AM, Igor Mammedov wrote:
> Hang is observed on virtual machines during CPU hotplug,
> especially in big guests with many CPUs. (It reproducible
> more often if host is over-committed).
>
> It happens because master CPU gives up waiting on
> secondary CPU and allows it to run wild. As result
> AP causes locking or crashing system. For example
> as described here: https://lkml.org/lkml/2014/3/6/257
>
> If master CPU have sent STARTUP IPI successfully,
> and AP signalled to master CPU that it's ready
> to start initialization, make master CPU wait
> indefinitely till AP is onlined.
> To ensure that AP won't ever run wild, make it
> wait at early startup till master CPU confirms its
> intention to wait for AP. If AP doesn't respond in 10
> seconds, the master CPU will timeout and cancel
> AP onlining.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
On Xen:
Tested-by: Boris Ostrovsky <boris.ostrovsky@orace.com>
next prev parent reply other threads:[~2014-06-24 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 12:23 [PATCH v7] x86: initialize secondary CPU only if master CPU will wait for it Igor Mammedov
2014-06-23 21:41 ` Toshi Kani
2014-06-24 17:25 ` Boris Ostrovsky [this message]
2014-07-02 9:26 ` Igor Mammedov
2014-08-04 10:44 ` Igor Mammedov
2014-08-28 11:57 ` Igor Mammedov
2014-09-16 10:58 ` [tip:x86/boot] x86/smpboot: Initialize " tip-bot for Igor Mammedov
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=53A9B485.9000303@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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