From: Ingo Molnar <mingo@kernel.org>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
konrad.wilk@oracle.com, david.vrabel@citrix.com,
tianyu.lan@intel.com, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/smp: Use die_complete completion when taking CPU down
Date: Thu, 16 Oct 2014 09:30:48 +0200 [thread overview]
Message-ID: <20141016073048.GA19055@gmail.com> (raw)
In-Reply-To: <1413384910-1231-1-git-send-email-boris.ostrovsky@oracle.com>
* Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:
> diff --git a/arch/x86/xen/smp.c b/arch/x86/xen/smp.c
> index 8650cdb..4da0008 100644
> --- a/arch/x86/xen/smp.c
> +++ b/arch/x86/xen/smp.c
> @@ -498,6 +498,7 @@ static int xen_cpu_disable(void)
> if (cpu == 0)
> return -EBUSY;
>
> + init_completion(&per_cpu(die_complete, smp_processor_id()));
> cpu_disable_common();
>
> load_cr3(swapper_pg_dir);
> @@ -510,6 +511,9 @@ static void xen_cpu_die(unsigned int cpu)
> current->state = TASK_UNINTERRUPTIBLE;
> schedule_timeout(HZ/10);
> }
> +
> + wait_for_completion_timeout(&per_cpu(die_complete, cpu), HZ);
> +
> xen_smp_intr_free(cpu);
> xen_uninit_lock_cpu(cpu);
> xen_teardown_timer(cpu);
So why not put it into cpu_disable_common() and do the same
change for native_cpu_disable()?
Likewise, the waiting bit should be put into a common function as
well (newly introduced, if need to be), we don't want to expose
internal x86 core data structures to the Xen guest code.
Thanks,
Ingo
prev parent reply other threads:[~2014-10-16 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 14:55 [PATCH] xen/smp: Use die_complete completion when taking CPU down Boris Ostrovsky
2014-10-16 7:30 ` Ingo Molnar [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=20141016073048.GA19055@gmail.com \
--to=mingo@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tianyu.lan@intel.com \
--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