From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
David Hildenbrand <david@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
Amit Shah <amit@kernel.org>
Subject: Re: [Qemu-devel] [PATCH v2] qdev: Mark devices as non-hotpluggable by default
Date: Mon, 25 Sep 2017 15:09:57 -0300 [thread overview]
Message-ID: <20170925180957.GE3030@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA_3SpWNm0FCviD5fXOFmxF1jGAwYgD_cZgwUMMAMn4BOQ@mail.gmail.com>
On Mon, Sep 25, 2017 at 07:05:26PM +0100, Peter Maydell wrote:
> On 25 September 2017 at 18:59, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > Finding the full list of devices that can be instantiated
> > internally at hotplug-time sounds tricky.
>
> If we just diff "list of devices marked hotplug before this patch"
> against "list of devices marked hotplug after this patch" how
> big is the list? Can we just eyeball it to see what needs
> to be specialcased?
I was working on a query-device-type QMP command some time ago.
I will rebase the work in progress and use it to build those
lists.
--
Eduardo
next prev parent reply other threads:[~2017-09-25 18:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 9:16 [Qemu-devel] [PATCH v2] qdev: Mark devices as non-hotpluggable by default Thomas Huth
2017-09-22 10:13 ` David Gibson
2017-09-25 10:13 ` Marcel Apfelbaum
2017-09-25 11:53 ` Cornelia Huck
2017-09-25 13:31 ` Eduardo Habkost
2017-09-25 13:46 ` Igor Mammedov
2017-09-25 14:34 ` Eduardo Habkost
2017-09-25 15:19 ` Thomas Huth
2017-09-25 15:26 ` Peter Maydell
2017-09-25 17:42 ` Thomas Huth
2017-09-25 17:45 ` Peter Maydell
2017-09-25 17:51 ` Eduardo Habkost
2017-09-25 18:02 ` Peter Maydell
2017-09-25 18:20 ` Eduardo Habkost
2017-09-25 18:46 ` Peter Maydell
2017-09-25 17:59 ` Eduardo Habkost
2017-09-25 18:05 ` Peter Maydell
2017-09-25 18:09 ` Eduardo Habkost [this message]
2017-09-26 2:59 ` Eduardo Habkost
2017-09-26 3:29 ` Thomas Huth
2017-09-26 16:11 ` Peter Maydell
2017-09-26 17:27 ` Thomas Huth
2017-09-26 18:00 ` Peter Maydell
2017-09-25 17:48 ` Eduardo Habkost
2017-09-26 5:26 ` Bharata B Rao
2017-09-26 10:20 ` Thomas Huth
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=20170925180957.GE3030@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=amit@kernel.org \
--cc=anthony.perard@citrix.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=imammedo@redhat.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 \
--cc=xiaoguangrong.eric@gmail.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).