From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen/x86: Don't BUG on CPU0 offlining
Date: Wed, 28 Jun 2017 11:44:24 -0400 [thread overview]
Message-ID: <20170628154424.GH30116@char.us.oracle.com> (raw)
In-Reply-To: <20170626163930.29697-1-vkuznets@redhat.com>
On Mon, Jun 26, 2017 at 06:39:30PM +0200, Vitaly Kuznetsov wrote:
> CONFIG_BOOTPARAM_HOTPLUG_CPU0 allows to offline CPU0 but Xen HVM guests
> BUG() in xen_teardown_timer(). Remove the BUG_ON(), this is probably a
> leftover from ancient times when CPU0 hotplug was impossible, it works
> just fine for HVM.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Perhaps:
BUG_ON(cpu == 0 && xen_pv_domain());
?
> ---
> - CPU0 hotplug is currently broken on x86, see
> https://lkml.org/lkml/2017/6/26/529
> ---
> arch/x86/xen/time.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
> index a1895a8..1ecb05d 100644
> --- a/arch/x86/xen/time.c
> +++ b/arch/x86/xen/time.c
> @@ -309,7 +309,6 @@ static irqreturn_t xen_timer_interrupt(int irq, void *dev_id)
> void xen_teardown_timer(int cpu)
> {
> struct clock_event_device *evt;
> - BUG_ON(cpu == 0);
> evt = &per_cpu(xen_clock_events, cpu).evt;
>
> if (evt->irq >= 0) {
> --
> 2.9.4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-28 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 16:39 [PATCH] xen/x86: Don't BUG on CPU0 offlining Vitaly Kuznetsov
2017-06-28 15:44 ` Konrad Rzeszutek Wilk [this message]
2017-06-28 16:31 ` [Xen-devel] " Vitaly Kuznetsov
2017-06-29 7:02 ` Juergen Groß
2017-07-18 8:00 ` Juergen Gross
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=20170628154424.GH30116@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.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