From: julien.grall@citrix.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] xen/arm: don't try to re-register vcpu_info on cpu_hotplug.
Date: Fri, 16 Oct 2015 17:49:35 +0100 [thread overview]
Message-ID: <56212A9F.5070202@citrix.com> (raw)
In-Reply-To: <1445013301-12624-3-git-send-email-stefano.stabellini@eu.citrix.com>
Hi Stefano,
On 16/10/15 17:35, Stefano Stabellini wrote:
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
> arch/arm/xen/enlighten.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/xen/enlighten.c b/arch/arm/xen/enlighten.c
> index 6c09cc4..b193811 100644
> --- a/arch/arm/xen/enlighten.c
> +++ b/arch/arm/xen/enlighten.c
> @@ -93,6 +93,16 @@ static void xen_percpu_init(void)
> int err;
> int cpu = get_cpu();
>
> + /*
> + * VCPUOP_register_vcpu_info cannot be called twice for the same
> + * vcpu, so if vcpu_info is already registered, just get out. This
> + * can happen with cpu-hotplug.
> + */
> + if (per_cpu(xen_vcpu, cpu) != NULL) {
> + put_cpu();
> + return;
> + }
Not really related to this patch. By side effect this patch is also not
calling irq_percpu_enable.
Looking around, all the caller of irq_percpu_enable will call
irq_percpu_disable when the CPU is dying. Is there any side effect to
not doing this?
Regards,
> +
> pr_info("Xen: initializing cpu%d\n", cpu);
> vcpup = per_cpu_ptr(xen_vcpu_info, cpu);
>
>
--
Julien Grall
next prev parent reply other threads:[~2015-10-16 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:33 [PATCH v2] xen,arm: enable cpu_hotplug Stefano Stabellini
2015-10-16 16:34 ` [PATCH v2 1/3] xen/arm: Enable cpu_hotplug.c Stefano Stabellini
2015-10-16 16:40 ` Julien Grall
2015-10-16 16:35 ` [PATCH v2 2/3] xen, cpu_hotplug: call device_offline instead of cpu_down Stefano Stabellini
2015-10-16 16:35 ` [PATCH v2 3/3] xen/arm: don't try to re-register vcpu_info on cpu_hotplug Stefano Stabellini
2015-10-16 16:49 ` Julien Grall [this message]
2015-10-19 10:10 ` Stefano Stabellini
2015-10-19 10:27 ` Julien Grall
2015-10-19 16:50 ` Stefano Stabellini
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=56212A9F.5070202@citrix.com \
--to=julien.grall@citrix.com \
--cc=linux-arm-kernel@lists.infradead.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).