All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: qemu-stable@nongnu.org, qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: Fix rate limit
Date: Tue, 3 Dec 2013 12:21:29 -0500 (EST)	[thread overview]
Message-ID: <223842567.34743368.1386091289854.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20131203171822.GA15093@srcf.ucam.org>

> On Mon, Nov 25, 2013 at 02:42:43PM -0500, Matthew Garrett wrote:
> > The migration thread appears to want to allow writeout to occur at full
> > speed rather than being rate limited during completion of state saving,
> > but sets the limit to INT_MAX when xfer_limit is INT64_MAX. This causes
> > problems if there's more than 2GB of state left to save at this point. It
> > probably ought to just be INT64_MAX instead.
> > 
> > Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
> > ---
> >  migration.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/migration.c b/migration.c
> > index 2b1ab20..ff00bfb 100644
> > --- a/migration.c
> > +++ b/migration.c
> > @@ -583,7 +583,7 @@ static void *migration_thread(void *opaque)
> >  
> >                  ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE);
> >                  if (ret >= 0) {
> > -                    qemu_file_set_rate_limit(s->file, INT_MAX);
> > +                    qemu_file_set_rate_limit(s->file, INT64_MAX);
> >                      qemu_savevm_state_complete(s->file);
> >                  }
> >                  qemu_mutex_unlock_iothread();
> > --
> > 1.8.4.2


I didn't see this,

Cc: qemu-stable@nongnu.org
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

      reply	other threads:[~2013-12-03 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 19:42 [Qemu-devel] [PATCH] migration: Fix rate limit Matthew Garrett
2013-12-03 17:18 ` Matthew Garrett
2013-12-03 17:21   ` Paolo Bonzini [this message]

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=223842567.34743368.1386091289854.JavaMail.root@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 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.