All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
	 "Dr . David Alan Gilbert" <dave@treblig.org>,
	Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH] hmp/migration: Fix documents for "migrate" command
Date: Fri, 03 May 2024 08:58:09 +0200	[thread overview]
Message-ID: <87fruz1iwu.fsf@pond.sub.org> (raw)
In-Reply-To: <20240502154729.370938-1-peterx@redhat.com> (Peter Xu's message of "Thu, 2 May 2024 11:47:29 -0400")

Peter Xu <peterx@redhat.com> writes:

> Peter missed the Sphinx HMP document for the "resume/-r" flag in commit
> 7a4da28b26 ("qmp: hmp: add migrate "resume" option").  Add it.  Avoid
> adding a Fixes to make life easier for the stable maintainer.

I'm curious: how does not adding Fixes: make life easier?

> When at it, slightly cleanup the lines, move "detach/-d" to a separate
> section rather than appending it at the end of the command description.
>
> Cc: Dr. David Alan Gilbert <dave@treblig.org>
> Cc: Fabiano Rosas <farosas@suse.de>
> Cc: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>
> Based-on: <20240430142737.29066-1-farosas@suse.de>
> ("[PATCH v3 0/6] migration removals & deprecations")
> ---
>  hmp-commands.hx | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/hmp-commands.hx b/hmp-commands.hx
> index ebca2cdced..484a8a1c3a 100644
> --- a/hmp-commands.hx
> +++ b/hmp-commands.hx
> @@ -918,8 +918,13 @@ ERST
       {
           .name       = "migrate",
           .args_type  = "detach:-d,blk:-b,inc:-i,resume:-r,uri:s",
           .params     = "[-d] [-b] [-i] [-r] uri",
           .help       = "migrate to URI (using -d to not wait for completion)"
                         "\n\t\t\t -b for migration without shared storage with"
                         " full copy of disk\n\t\t\t -i for migration without "
                         "shared storage with incremental copy of disk "
                         "(base image shared between src and destination)"
                         "\n\t\t\t -r to resume a paused migration",
           .cmd        = hmp_migrate,
       },
>  
>  
>  SRST
> -``migrate [-d]`` *uri*
> -  Migrate to *uri* (using -d to not wait for completion).
> +``migrate [-d] [-r]`` *uri*
> +  Migrate the current VM to *uri*.

Could there be any other VM than the current one?  Scratch "current"?

> +
> +  ``-d``
> +    Run this command asynchronously, so that the command doesn't wait for completion.

What is run asynchronously, and what isn't waiting?  These are two
different entities, aren't they?  Calling them "this command" and "the
command" is confusing :)

Perhaps

       Start the migration process, but do not wait for its completion.

Maybe add a hint on how to wait or poll for completion?

> +  ``-r``
> +    Resume a paused postcopy migration.

.help doesn't have "postcopy".  Should it?

>  ERST
>  
>      {



  parent reply	other threads:[~2024-05-03  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02 15:47 [PATCH] hmp/migration: Fix documents for "migrate" command Peter Xu
2024-05-02 17:34 ` Fabiano Rosas
2024-05-03  6:58 ` Markus Armbruster [this message]
2024-05-03 13:54   ` Peter Xu
2024-05-03 14:08     ` Markus Armbruster
2024-05-03 14:36       ` Peter Xu

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=87fruz1iwu.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=dave@treblig.org \
    --cc=farosas@suse.de \
    --cc=peterx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.