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: zhang.zhanghailiang@huawei.com, quintela@redhat.com,
	liang.z.li@intel.com, qemu-devel@nongnu.org, jdenemar@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/6] Migration: Emit event at start of pass
Date: Wed, 13 Jan 2016 15:57:22 +0530	[thread overview]
Message-ID: <20160113102632.GD17885@grmbl.mre> (raw)
In-Reply-To: <20151216165214.GB2604@work-vm>

On (Wed) 16 Dec 2015 [16:52:14], Dr. David Alan Gilbert wrote:
> * Eric Blake (eblake@redhat.com) wrote:
> > On 12/16/2015 04:47 AM, Dr. David Alan Gilbert (git) wrote:
> > > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > > 
> > > Emit an event each time we sync the dirty bitmap on the source;
> > > this helps libvirt use postcopy by giving it a kick when it
> > > might be a good idea to start the postcopy.
> > > 
> > > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > > ---
> > >  docs/qmp-events.txt | 14 ++++++++++++++
> > >  migration/ram.c     |  4 ++++
> > >  qapi/event.json     | 13 +++++++++++++
> > >  3 files changed, 31 insertions(+)
> > > 
> > 
> > >  
> > > +MIGRATION_PASS
> > > +--------------
> > > +
> > > +Emitted from the source side of a migration at the start of each pass
> > > +(when it syncs the dirty bitmap)
> > > +
> > > +Data: None.
> > > +
> > > +  - "pass": An incrementing count (starting at 1 on the first pass)
> > > +
> > > +Example:
> > > +{"timestamp": {"seconds": 1449669631, "microseconds": 239225},
> > > + "event": "MIGRATION_PASS", "data": {"pass": 2}}
> > 
> > How frequently can this event be emitted?  It is not under guest
> > control, so it's harder to argue that it could be abused as a way for
> > the guest to DoS the host.  And hopefully it is slow enough (considering
> > that each pass also requires lots more effort for actually transmitting
> > state from source to dest), so I don't think we have to worry about
> > adding rate-limiting to avoid overwhelming the monitor client.
> 
> The only way that you'd get a rapid repetition of the events
> is if the pass was very short.  However a very short pass is normally
> the signal to exit the iterative loop of migration and send the
> last blob at the end of migration.  And that definition of 'short' is
> determined by the downtime set by the management layer anyway.

Yes, and this can also give us stats on how quickly migration is
progressing.

		Amit

  reply	other threads:[~2016-01-13 10:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 11:47 [Qemu-devel] [PATCH v2 0/6] Migration: Small fixes and improvements Dr. David Alan Gilbert (git)
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 1/6] migration: Export migrate_set_state() Dr. David Alan Gilbert (git)
2015-12-16 12:40   ` Juan Quintela
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 2/6] migration: Add state records for migration incoming Dr. David Alan Gilbert (git)
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 3/6] Postcopy: Send events/change state on incoming side Dr. David Alan Gilbert (git)
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 4/6] Migration: Emit event at start of pass Dr. David Alan Gilbert (git)
2015-12-16 12:41   ` Juan Quintela
2015-12-16 16:47   ` Eric Blake
2015-12-16 16:52     ` Dr. David Alan Gilbert
2016-01-13 10:27       ` Amit Shah [this message]
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 5/6] Use qemu_get_buffer_in_place for xbzrle data Dr. David Alan Gilbert (git)
2015-12-16 11:47 ` [Qemu-devel] [PATCH v2 6/6] multithread decompression: Avoid one copy Dr. David Alan Gilbert (git)
2016-01-13 10:29 ` [Qemu-devel] [PATCH v2 0/6] Migration: Small fixes and improvements 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=20160113102632.GD17885@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zhang.zhanghailiang@huawei.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).