From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>
Cc: John Snow <jsnow@redhat.com>,
amit.shah@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
quintela@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
marcandre.lureau@redhat.com, groug@kaod.org,
aneesh.kumar@linux.vnet.ibm.com,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] migration: Add a new option to enable only-migratable
Date: Thu, 15 Dec 2016 16:50:02 +0000 [thread overview]
Message-ID: <20161215165001.GP2509@work-vm> (raw)
In-Reply-To: <CAC2QTZZxEfy0YU2uEjt-P3VrJJWPzGfUW-mvFyyrAiiBQ6LorA@mail.gmail.com>
* Ashijeet Acharya (ashijeetacharya@gmail.com) wrote:
> On Thu, Dec 15, 2016 at 8:59 PM, Dr. David Alan Gilbert
> <dgilbert@redhat.com> wrote:
> > * Ashijeet Acharya (ashijeetacharya@gmail.com) wrote:
> >> Add a new option "--only-migratable" in qemu which will allow to add
> >> only those devices which will not fail qemu after migration. Devices
> >> set with the flag 'unmigratable' cannot be added when this option will
> >> be used.
> >>
> >> Signed-off-by: Ashijeet Acharya <ashijeetacharya@gmail.com>
> >> ---
> >> include/migration/migration.h | 3 +++
> >> qemu-options.hx | 10 ++++++++++
> >> vl.c | 4 ++++
> >> 3 files changed, 17 insertions(+)
> >>
> >> diff --git a/include/migration/migration.h b/include/migration/migration.h
> >> index c309d23..40b3697 100644
> >> --- a/include/migration/migration.h
> >> +++ b/include/migration/migration.h
> >> @@ -38,6 +38,9 @@
> >> #define QEMU_VM_COMMAND 0x08
> >> #define QEMU_VM_SECTION_FOOTER 0x7e
> >>
> >> +/* for vl.c */
> >> +extern int only_migratable;
> >> +
> >> struct MigrationParams {
> >> bool blk;
> >> bool shared;
> >> diff --git a/qemu-options.hx b/qemu-options.hx
> >> index c534a2f..7cc2cc5 100644
> >> --- a/qemu-options.hx
> >> +++ b/qemu-options.hx
> >> @@ -3574,6 +3574,16 @@ be used to change settings (such as migration parameters) prior to issuing
> >> the migrate_incoming to allow the migration to begin.
> >> ETEXI
> >>
> >> +DEF("only-migratable", 0, QEMU_OPTION_only_migratable, \
> >> + "-only-migratable allow only migratable devices\n", QEMU_ARCH_ALL)
> >> +STEXI
> >> +@item -only-migratable
> >> +@findex -only-migratable
> >> +Don't allow adding devices that will fail QEMU after migration. Devices set with
> >> +the flag unmigratable are not allowed to be added neither statically nor
> >> +dynamically
> >> +ETEXI
> >
> > Can I suggest rewording that as:
> > Only allow migratable devices. Devices will not be allowed to enter an unmigratable
> > state.
>
> No problem, will fix that in v2.
>
> >> DEF("nodefaults", 0, QEMU_OPTION_nodefaults, \
> >> "-nodefaults don't create default devices\n", QEMU_ARCH_ALL)
> >> STEXI
> >> diff --git a/vl.c b/vl.c
> >> index d77dd86..82bffb9 100644
> >> --- a/vl.c
> >> +++ b/vl.c
> >> @@ -180,6 +180,7 @@ bool boot_strict;
> >> uint8_t *boot_splash_filedata;
> >> size_t boot_splash_filedata_size;
> >> uint8_t qemu_extra_params_fw[2];
> >> +int only_migratable = 0; /* turn it off unless user states otherwise */
> >>
> >> int icount_align_option;
> >>
> >> @@ -3914,6 +3915,9 @@ int main(int argc, char **argv, char **envp)
> >> }
> >> incoming = optarg;
> >> break;
> >> + case QEMU_OPTION_only_migratable:
> >> + only_migratable = 1;
> >> + break;
> >> case QEMU_OPTION_nodefaults:
> >> has_defaults = 0;
> >> break;
> >
> > Does this need to go in the 'first pass of option parsing' loop
> > to make sure that it doesn't matter which order it's in and it
> > stops other devices on the command line?
>
> I am not sure what you meant by order here;
>
> Do you mean the order as in the place --only-migratable is used,
>
> 1. ./bin/qemu-system-x86_64 -m 1024 -name f15 -device
> nec-usb-xhci,id=xhci -device usb-uas,id=uas,bus=xhci.0
> --only-migratable
> 2. ./bin/qemu-system-x86_64 -m 1024 -name f15 --only-migratable
> -device nec-usb-xhci,id=xhci -device usb-uas,id=uas,bus=xhci.0
>
> Because I have tested both and they seem to be working equally fine.
> Sorry if I understood wrong.
If that works OK that's fine, no change needed.
Dave
>
> Ashijeet
>
> > Dave
> >
> >> --
> >> 2.6.2
> >>
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-12-15 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 19:06 [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option Ashijeet Acharya
2016-12-14 19:07 ` [Qemu-devel] [PATCH 1/3] migration: Add a new option to enable only-migratable Ashijeet Acharya
2016-12-15 15:29 ` Dr. David Alan Gilbert
2016-12-15 16:48 ` Ashijeet Acharya
2016-12-15 16:50 ` Dr. David Alan Gilbert [this message]
2016-12-14 19:07 ` [Qemu-devel] [PATCH 2/3] migration: Allow "device add" options to only add migratable devices Ashijeet Acharya
2016-12-15 16:05 ` Dr. David Alan Gilbert
2016-12-15 16:10 ` Ashijeet Acharya
2016-12-15 16:19 ` Dr. David Alan Gilbert
2016-12-15 16:36 ` Ashijeet Acharya
2016-12-14 19:07 ` [Qemu-devel] [PATCH 3/3] migration: disallow migrate_add_blocker during migration Ashijeet Acharya
2016-12-15 17:11 ` Dr. David Alan Gilbert
2016-12-15 17:51 ` John Snow
2016-12-15 18:12 ` Ashijeet Acharya
2016-12-15 15:57 ` [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option Michael S. Tsirkin
2016-12-15 16:07 ` Dr. David Alan Gilbert
2016-12-15 16:16 ` Ashijeet Acharya
2016-12-15 18:53 ` Michael S. Tsirkin
2016-12-15 19:03 ` Dr. David Alan Gilbert
2016-12-15 19:16 ` Peter Maydell
2016-12-15 19:39 ` Dr. David Alan Gilbert
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=20161215165001.GP2509@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=ashijeetacharya@gmail.com \
--cc=groug@kaod.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).