From: Juergen Gross <jgross@suse.com>
To: Olaf Hering <olaf@aepfle.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xenproject.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] xen: avoid crash in disable_hotplug_cpu
Date: Tue, 11 Sep 2018 09:55:07 +0200 [thread overview]
Message-ID: <6b51f88f-7f40-ded4-0202-e4c31fa606a2@suse.com> (raw)
In-Reply-To: <20180911095258.5ed9e9b7.olaf@aepfle.de>
On 11/09/18 09:52, Olaf Hering wrote:
> Am Fri, 7 Sep 2018 12:56:37 -0400
> schrieb Boris Ostrovsky <boris.ostrovsky@oracle.com>:
>
>> I was hoping you'd respond to my question about warning.
>
> It looks like CONFIG_BOOTPARAM_HOTPLUG_CPU0=y is the reason for the warning.
> As Jürgen suggested in another mail, Xen should probably disable hotplugging
> for cpu#0 in the generic setup code. Then cpu_is_hotpluggable(cpu) would
> do the right thing.
>
> Do you want me to merge that extra change into this patch?
I think an extra patch would be better, as it is a different issue.
Juergen
next prev parent reply other threads:[~2018-09-11 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 14:31 [PATCH v4] xen: avoid crash in disable_hotplug_cpu Olaf Hering
2018-09-07 14:34 ` Juergen Gross
2018-09-07 14:34 ` Juergen Gross
2018-09-07 16:56 ` Boris Ostrovsky
2018-09-10 15:58 ` Olaf Hering
2018-09-10 15:58 ` Olaf Hering
2018-09-10 17:55 ` Boris Ostrovsky
2018-09-10 17:55 ` Boris Ostrovsky
2018-09-11 7:52 ` Olaf Hering
2018-09-11 7:52 ` Olaf Hering
2018-09-11 7:55 ` Juergen Gross
2018-09-11 7:55 ` Juergen Gross [this message]
2018-09-11 10:48 ` Olaf Hering
2018-09-11 10:48 ` Olaf Hering
2018-09-11 10:51 ` Juergen Gross
2018-09-11 10:51 ` Juergen Gross
2018-09-07 16:56 ` Boris Ostrovsky
2018-09-11 19:39 ` Boris Ostrovsky
2018-09-11 19:39 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2018-09-07 14:31 Olaf Hering
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=6b51f88f-7f40-ded4-0202-e4c31fa606a2@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.