qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: quintela@redhat.com, liang.z.li@intel.com, mjt@tls.msk.ru,
	qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/3] -incoming pause
Date: Wed, 18 Feb 2015 11:13:11 +0530	[thread overview]
Message-ID: <20150218054311.GD19354@grmbl.mre> (raw)
In-Reply-To: <20150217201324.GI2291@work-vm>

On (Tue) 17 Feb 2015 [20:13:25], Dr. David Alan Gilbert wrote:
> * Eric Blake (eblake@redhat.com) wrote:
> > On 02/17/2015 07:59 AM, Amit Shah wrote:
> > >>>
> > >>> So the only comment I have is with the 'pause' name.
> > >>>
> > >>> 'pause' to me means there's a time period for which a pause has to be
> > >>> done; or pausing an activity which is already in progress, both of
> > >>> which are not true for this case.
> > >>
> > >> I think that pause and wait are both pretty similar; wait generally
> > >> does mean wait for something specific though.
> > >>
> > >> The 'pause' button on your video player doesn't have an expectation
> > >> of how long you will pause it.
> > > 
> > > Right; but it pauses an already-playing video.  We're not pausing an
> > > incoming migration here; we're not even started.
> > > 
> > > So pause in the migration world will make sense (to me, of course)
> > > when we actually pause an ongoing migration...
> > 
> > As long as we are bike-shedding, would 'defer' be any nicer, as an
> > indication that we are deferring the actual migration until the QMP
> > command starts it?
> 
> I'm happy with any of them (as I assume were those who R-b'd the set).
> 
> If people really think it needs to change then fine, I'm happy
> to recut and retest it.  But if it's just bike-shedding, then I'd
> rather not.

One of the reasons for me raising this is the line:

'Pausing an already paused guest'

comparing that to:

'Incoming migration already deferred'

or some construct like that is much clearer.

The former just adds to the confusion and the mess we have with
migration error messages.  You've already done a good job fixing many
of our existing error and debug messages, so it'll be great to avoid
introducing one.

Thanks,

		Amit

  reply	other threads:[~2015-02-18  5:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 16:46 [Qemu-devel] [PATCH v2 0/3] -incoming pause Dr. David Alan Gilbert (git)
2015-02-11 16:46 ` [Qemu-devel] [PATCH v2 1/3] Add " Dr. David Alan Gilbert (git)
2015-02-11 16:46 ` [Qemu-devel] [PATCH v2 2/3] Add migrate_incoming Dr. David Alan Gilbert (git)
2015-02-11 17:19   ` Eric Blake
2015-02-11 18:24     ` Juan Quintela
2015-02-11 18:20   ` Juan Quintela
2015-02-11 18:22     ` Dr. David Alan Gilbert
2015-02-11 16:46 ` [Qemu-devel] [PATCH v2 3/3] Document -incoming options Dr. David Alan Gilbert (git)
2015-02-17 12:46 ` [Qemu-devel] [PATCH v2 0/3] -incoming pause Amit Shah
2015-02-17 13:27   ` Dr. David Alan Gilbert
2015-02-17 14:59     ` Amit Shah
2015-02-17 16:14       ` Eric Blake
2015-02-17 20:13         ` Dr. David Alan Gilbert
2015-02-18  5:43           ` Amit Shah [this message]
2015-02-18  5:40         ` Amit Shah

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=20150218054311.GD19354@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --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).