All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Juan Quintela <quintela@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Laurent Vivier <lvivier@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/5] Migration pull request
Date: Thu, 1 Jun 2017 15:50:27 +0100	[thread overview]
Message-ID: <CAFEAcA9O1cQRLV69TgNH6ezk3vckRXe4+WRK_HD0Ed9yk=mjvQ@mail.gmail.com> (raw)
In-Reply-To: <20170531091538.21626-1-quintela@redhat.com>

On 31 May 2017 at 10:15, Juan Quintela <quintela@redhat.com> wrote:
> Hi
>
> This are the migration patches ready for inclusion:
> - autoconverge improvements: (felipe franciosi)
> - create savem.h
>
> Please, Apply.
>
> The following changes since commit 0748b3526e8cb78b9cd64208426bfc3d54a72b04:
>
>   Merge remote-tracking branch 'kwolf/tags/for-upstream' into staging (2017-05-30 14:15:15 +0100)
>
> are available in the git repository at:
>
>   git://github.com/juanquintela/qemu.git tags/migration/20170531
>
> for you to fetch changes up to b4a3c64b16856a018869bfd4a9ed3b2a74554541:
>
>   migration: use dirty_rate_high_cnt more aggressively (2017-05-31 09:39:20 +0200)
>
> ----------------------------------------------------------------
> migration/next for 20170531
>
> ----------------------------------------------------------------
> Felipe Franciosi (4):
>       migration: keep bytes_xfer_prev init'd to zero
>       migration: set dirty_pages_rate before autoconverge logic
>       migration: set bytes_xfer_* outside of autoconverge logic
>       migration: use dirty_rate_high_cnt more aggressively
>
> Juan Quintela (1):
>       migration: Create savevm.h for functions exported from savevm.c

Applied, thanks.

-- PMM

  parent reply	other threads:[~2017-06-01 14:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  9:15 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-05-31  9:15 ` [Qemu-devel] [PULL 1/5] migration: Create savevm.h for functions exported from savevm.c Juan Quintela
2017-05-31  9:15 ` [Qemu-devel] [PULL 2/5] migration: keep bytes_xfer_prev init'd to zero Juan Quintela
2017-05-31  9:15 ` [Qemu-devel] [PULL 3/5] migration: set dirty_pages_rate before autoconverge logic Juan Quintela
2017-05-31  9:15 ` [Qemu-devel] [PULL 4/5] migration: set bytes_xfer_* outside of " Juan Quintela
2017-05-31  9:15 ` [Qemu-devel] [PULL 5/5] migration: use dirty_rate_high_cnt more aggressively Juan Quintela
2017-06-01 14:50 ` Peter Maydell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-04  4:21 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2018-06-04  4:29 ` no-reply
2018-06-04  7:30   ` Juan Quintela
2018-06-04 13:24 ` Peter Maydell
2017-06-14 11:51 [Qemu-devel] [PULL 0/5] Migration PULL request Juan Quintela
2017-06-15 11:56 ` Peter Maydell
2017-05-12 15:52 [Qemu-devel] [PULL 0/5] Migration pull request Juan Quintela
2017-05-15 13:58 ` Stefan Hajnoczi
2017-05-15 14:52   ` Eric Blake
2017-05-15 17:17   ` Juan Quintela
2017-05-16 14:35 ` Stefan Hajnoczi
2015-11-04 12:48 Juan Quintela
2015-11-05 10:48 ` Peter Maydell

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='CAFEAcA9O1cQRLV69TgNH6ezk3vckRXe4+WRK_HD0Ed9yk=mjvQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@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 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.