From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] qdev: Make "hotplugged" property read-only
Date: Tue, 3 Jan 2017 17:53:27 +0100 [thread overview]
Message-ID: <20170103175327.61778555@Igors-MacBook-Pro.local> (raw)
In-Reply-To: <e27ac12b-9e41-f145-ca05-385d4edd2738@redhat.com>
On Tue, 3 Jan 2017 17:10:15 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> On 03/01/2017 15:22, Eduardo Habkost wrote:
> >> I didn't know that. Is this documented somewhere?
> >> Is it actually used by any existing software?
> > not that I know of. But users should be fixed if they are not using it.
> >
> > I see. The problem is that the mechanism is undocumented,
> > untested, and seems very likely to trigger bugs in device code.
>
> I agree. Why can't hotplugged be migrated?
It's probably not migrated because of it's not runtime/guest modified
state so we don't have to migrate it as it's know in advance.
For now it should set manually on CLI (-device) with the rest of
hotplugged device properties.
> Paolo
next prev parent reply other threads:[~2017-01-03 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 22:38 [Qemu-devel] [PATCH] qdev: Make "hotplugged" property read-only Eduardo Habkost
2016-12-30 14:28 ` Igor Mammedov
2016-12-30 18:23 ` Eduardo Habkost
2017-01-03 13:02 ` Igor Mammedov
2017-01-03 14:22 ` Eduardo Habkost
2017-01-03 15:07 ` Igor Mammedov
2017-01-03 16:10 ` Paolo Bonzini
2017-01-03 16:53 ` Igor Mammedov [this message]
2017-01-03 17:06 ` Eduardo Habkost
2017-02-22 19:21 ` Eduardo Habkost
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=20170103175327.61778555@Igors-MacBook-Pro.local \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).