public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.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 18:31:59 +0200	[thread overview]
Message-ID: <877ezwvzsw.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20170628154424.GH30116@char.us.oracle.com> (Konrad Rzeszutek Wilk's message of "Wed, 28 Jun 2017 11:44:24 -0400")

Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> writes:

> 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()); 
>

Linus says no BUG_ONs :-)

xen_pv_cpu_disable() has the following:

    if (cpu == 0)
            return -EBUSY;

as a protection so we won't get to xen_teardown_timer() but if you think
additional BUG_ON() protection is justified I'm definitely not against
adding it.

-- 
  Vitaly

  reply	other threads:[~2017-06-28 16:32 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 ` [Xen-devel] " Konrad Rzeszutek Wilk
2017-06-28 16:31   ` Vitaly Kuznetsov [this message]
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=877ezwvzsw.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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