qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, dgilbert@redhat.com
Subject: [Qemu-devel] [PULL 0/6] Migration pull request
Date: Wed, 30 Sep 2015 10:56:00 +0200	[thread overview]
Message-ID: <1443603366-4686-1-git-send-email-quintela@redhat.com> (raw)

Hi

This get the auto-converge changes for migration, please pull.


The following changes since commit b2312c680084ea18cd55fa7093397cad2224ec14:

  Merge remote-tracking branch 'remotes/amit-migration/tags/for-juan-201509' into staging (2015-09-29 12:41:19 +0100)

are available in the git repository at:

  git://github.com/juanquintela/qemu.git tags/migration/20150930

for you to fetch changes up to dc3256272cf70b2152279b013a8abb16e0f6fe96:

  migration: Disambiguate MAX_THROTTLE (2015-09-30 09:42:04 +0200)

----------------------------------------------------------------
migration/next for 20150930

----------------------------------------------------------------
Jason J. Herne (5):
      cpu: Provide vcpu throttling interface
      migration: Parameters for auto-converge cpu throttling
      migration: Dynamic cpu throttling for auto-converge
      qmp/hmp: Add throttle ratio to query-migrate and info migrate
      migration: Disambiguate MAX_THROTTLE

Juan Quintela (1):
      migration: yet more possible state transitions

 cpus.c                | 78 ++++++++++++++++++++++++++++++++++++++++++++
 hmp.c                 | 21 ++++++++++++
 include/qom/cpu.h     | 42 ++++++++++++++++++++++++
 migration/migration.c | 57 +++++++++++++++++++++++++++++++--
 migration/ram.c       | 89 +++++++++++++++++----------------------------------
 qapi-schema.json      | 40 ++++++++++++++++++++---
 vl.c                  |  1 +
 7 files changed, 263 insertions(+), 65 deletions(-)

             reply	other threads:[~2015-09-30  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  8:56 Juan Quintela [this message]
2015-09-30  8:56 ` [Qemu-devel] [PULL 1/6] migration: yet more possible state transitions Juan Quintela
2015-09-30  8:56 ` [Qemu-devel] [PULL 2/6] cpu: Provide vcpu throttling interface Juan Quintela
2015-09-30  8:56 ` [Qemu-devel] [PULL 3/6] migration: Parameters for auto-converge cpu throttling Juan Quintela
2015-09-30  8:56 ` [Qemu-devel] [PULL 4/6] migration: Dynamic cpu throttling for auto-converge Juan Quintela
2015-09-30  8:56 ` [Qemu-devel] [PULL 5/6] qmp/hmp: Add throttle ratio to query-migrate and info migrate Juan Quintela
2015-09-30  8:56 ` [Qemu-devel] [PULL 6/6] migration: Disambiguate MAX_THROTTLE Juan Quintela
2015-10-01 11:01 ` [Qemu-devel] [PULL 0/6] Migration pull request Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2015-11-12 17:20 Juan Quintela
2015-11-12 18:52 ` Peter Maydell
2015-07-15  9:04 Juan Quintela
2015-07-15 10:16 ` Amit Shah
2015-07-15 13:19   ` Peter Maydell
2015-07-15 13:39     ` Juan Quintela
2015-07-15 10:20 ` Juan Quintela

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=1443603366-4686-1-git-send-email-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@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 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).