From: Igor Mammedov <imammedo@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Anthony Perard <anthony.perard@citrix.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] qdev: Mark devices as non-hotpluggable by default
Date: Thu, 21 Sep 2017 10:04:06 +0200 [thread overview]
Message-ID: <20170921100406.11fbc2ed@nial.brq.redhat.com> (raw)
In-Reply-To: <05454839-2216-ee27-1cce-7d9899563806@redhat.com>
On Wed, 20 Sep 2017 18:10:48 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 20.09.2017 13:17, Thomas Huth wrote:
> > On 20.09.2017 12:57, Marcel Apfelbaum wrote:
> >> On 20/09/2017 13:07, Peter Maydell wrote:
> [...]
> >>> Is it possible to hack together some kind of test code that
> >>> can give us a list of the devices compiled in that have
> >>> hotpluggable enabled? Then we could compare before and
> >>> after to see which devices we've changed.
> >>>
> >>
> >> Eduardo came up with some cool automated tests not long ago.
> >> Eduardo, can your tests help?
> >
> > You mean the scripts/device-crash-test script? That's only for
> > cold-plugging ... but I could maybe use the device_add HMP test (see
> > https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg00817.html ) to
> > exercise the hotplugging of all devices and add some debug code to
> > qdev_device_add() to see which devices are dc->hotpluggable and have a
> > hotplug handler at the same time... I'll give it a try.
>
> Ok, done that now, and it looks like I missed devices of type
> TYPE_X86_CPU and TYPE_S390_CPU at least... Unlike the ppc64 CPUs, they
> are not derived from TYPE_CPU_CORE, but from TYPE_CPU ... is that on
> purpose? I thought hot-pluggable CPUs would need to be derived from
> TYPE_CPU_CORE... well, maybe I just understood that wrong.
> I'll send a new version of my patch.
cpu hotplug on x86 existed before ppc started to support it and
hotplug is done at thread level there. core was introduced later
for ppc as guest expects hotplugged cpu in core granularity.
So as you noticed some leaf CPU types are indeed hotpluggble.
>
> Thomas
next prev parent reply other threads:[~2017-09-21 8:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 8:55 [Qemu-devel] [RFC PATCH] qdev: Mark devices as non-hotpluggable by default Thomas Huth
2017-09-20 7:50 ` Marcel Apfelbaum
2017-09-20 10:07 ` Peter Maydell
2017-09-20 10:57 ` Marcel Apfelbaum
2017-09-20 11:17 ` Thomas Huth
2017-09-20 16:10 ` Thomas Huth
2017-09-20 16:15 ` David Hildenbrand
2017-09-21 8:04 ` Igor Mammedov [this message]
2017-09-21 15:27 ` Anthony PERARD
2017-09-21 18:50 ` Eduardo Habkost
2017-09-22 7:38 ` Cornelia Huck
2017-09-22 7:52 ` Thomas Huth
2017-09-22 7:47 ` Thomas Huth
2017-09-22 19:25 ` Cédric Le Goater
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=20170921100406.11fbc2ed@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=ehabkost@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=thuth@redhat.com \
/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).