From: Juan Quintela <quintela@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] migration: Disable hotplug/unplug during migration
Date: Tue, 28 Mar 2017 12:48:06 +0200 [thread overview]
Message-ID: <8760itsmmx.fsf@secure.mitica> (raw)
In-Reply-To: <20170324153218.05864a87@nial.brq.redhat.com> (Igor Mammedov's message of "Fri, 24 Mar 2017 15:32:18 +0100")
Igor Mammedov <imammedo@redhat.com> wrote:
> On Thu, 23 Mar 2017 21:50:24 +0100
> Juan Quintela <quintela@redhat.com> wrote:
>
>> Until we have reviewed what can/can't be hotplug during migration,
>> disable it. We can enable it later for the things that we know that
>> work. For instance, memory hotplug during postcopy don't work
>> currently.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>> hw/core/qdev.c | 5 +++++
>> qdev-monitor.c | 7 ++++++-
>> 2 files changed, 11 insertions(+), 1 deletion(-)
>>
>> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
>> index 1e7fb33..8c4a3f3 100644
>> --- a/hw/core/qdev.c
>> +++ b/hw/core/qdev.c
>> @@ -277,6 +277,11 @@ void qdev_unplug(DeviceState *dev, Error **errp)
>> HotplugHandler *hotplug_ctrl;
>> HotplugHandlerClass *hdc;
>>
>> + if (!migration_is_idle()) {
>> + error_setg(errp, "device_add not allowed while migrating");
> s/device_add/device_del/
>
>
> I'd put this check after "if (!dc->hotpluggable)" block, so error
> message won't hide wrong upluggable device error cases
Thanks.
I did both changes. Not sure yet what *should* came 1st:
- device is not plugable/unplugable
- you can't do it while on migration
But I don't care, and as you seemed to preffer that other way, changed.
Later, Juan.
>> + return;
>> + }
>> +
>> if (dev->parent_bus && !qbus_is_hotpluggable(dev->parent_bus)) {
>> error_setg(errp, QERR_BUS_NO_HOTPLUG, dev->parent_bus->name);
>> return;
>> diff --git a/qdev-monitor.c b/qdev-monitor.c
>> index 5f2fcdf..e0622b4 100644
>> --- a/qdev-monitor.c
>> +++ b/qdev-monitor.c
>> @@ -29,7 +29,7 @@
>> #include "qemu/error-report.h"
>> #include "qemu/help_option.h"
>> #include "sysemu/block-backend.h"
>> -
>> +#include "migration/migration.h"
>> /*
>> * Aliases were a bad idea from the start. Let's keep them
>> * from spreading further.
>> @@ -566,6 +566,11 @@ DeviceState *qdev_device_add(QemuOpts *opts, Error **errp)
>> BusState *bus = NULL;
>> Error *err = NULL;
>>
>> + if (!migration_is_idle()) {
>> + error_setg(errp, "device_add not allowed while migrating");
>> + return NULL;
>> + }
> the same here, do it right before "/* create device */"
>
>> driver = qemu_opt_get(opts, "driver");
>> if (!driver) {
>> error_setg(errp, QERR_MISSING_PARAMETER, "driver");
next prev parent reply other threads:[~2017-03-28 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 20:50 [Qemu-devel] [RFC 0/2] Disable hotplug during migration Juan Quintela
2017-03-23 20:50 ` [Qemu-devel] [PATCH 1/2] migration: Disable hotplug/unplug " Juan Quintela
2017-03-24 9:48 ` Thomas Huth
2017-03-24 9:50 ` Juan Quintela
2017-03-24 14:32 ` Igor Mammedov
2017-03-28 10:48 ` Juan Quintela [this message]
2017-03-23 20:50 ` [Qemu-devel] [PATCH 2/2] ram: remove migration_bitmap_extend() Juan Quintela
2017-03-28 18:03 ` [Qemu-devel] [RFC 0/2] Disable hotplug during migration Dr. David Alan Gilbert
2017-03-29 10:40 ` Juan Quintela
2017-03-29 10:41 ` Juan Quintela
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=8760itsmmx.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@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).