From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xenproject.org, Juergen Gross <jgross@suse.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] xen: avoid crash in disable_hotplug_cpu
Date: Tue, 11 Sep 2018 12:48:08 +0200 [thread overview]
Message-ID: <20180911124808.18dfe8bf.olaf@aepfle.de> (raw)
In-Reply-To: <20180911095258.5ed9e9b7.olaf@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
Am Tue, 11 Sep 2018 09:52:58 +0200
schrieb Olaf Hering <olaf@aepfle.de>:
> 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.
The relevant code is all private to arch/x86/kernel/topology.c.
There is no way to set .hotpluggable prior to register_cpu.
I guess you need to work that out with the x86 maintainers.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-09-11 10:48 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-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
2018-09-11 10:48 ` Olaf Hering [this message]
2018-09-11 10:51 ` Juergen Gross
2018-09-11 10:51 ` Juergen Gross
2018-09-11 10:48 ` Olaf Hering
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=20180911124808.18dfe8bf.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.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 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.