qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Juan Quintela <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	qemu list <qemu-devel@nongnu.org>,
	duanj@linux.vnet.ibm.com, Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] [PULL 0/4] migration: QTAILQ migration
Date: Thu,  5 Jan 2017 22:02:06 +0530	[thread overview]
Message-ID: <1483633930-7103-1-git-send-email-amit.shah@redhat.com> (raw)

The following changes since commit dbe2b65566e76d3c3a0c3358285c0336ac61e757:

  Merge remote-tracking branch 'remotes/vivier/tags/m68k-for-2.9-pull-request' into staging (2016-12-28 17:11:11 +0000)

are available in the git repository at:

  https://git.kernel.org/pub/scm/virt/qemu/amit/migration.git tags/migration-for-2.9-1

for you to fetch changes up to 8d0c57697abcc57166e918064d9a7f6c7316d01b:

  migration: add error_report (2017-01-04 19:21:26 +0530)

----------------------------------------------------------------
Migration: migrate QTAILQ infrastructure for vmstate

----------------------------------------------------------------



Jianjun Duan (4):
  migration: extend VMStateInfo
  migration: migrate QTAILQ
  tests/migration: Add test for QTAILQ migration
  migration: add error_report

 hw/display/virtio-gpu.c     |   8 +-
 hw/intc/s390_flic_kvm.c     |   8 +-
 hw/net/vmxnet3.c            |  24 ++++--
 hw/nvram/eeprom93xx.c       |   8 +-
 hw/nvram/fw_cfg.c           |   8 +-
 hw/pci/msix.c               |   8 +-
 hw/pci/pci.c                |  16 +++-
 hw/pci/shpc.c               |   7 +-
 hw/scsi/scsi-bus.c          |   8 +-
 hw/timer/twl92230.c         |   8 +-
 hw/usb/redirect.c           |  26 ++++--
 hw/virtio/virtio-pci.c      |   8 +-
 hw/virtio/virtio.c          |  15 +++-
 include/migration/vmstate.h |  39 +++++++--
 include/qemu/queue.h        |  60 ++++++++++++++
 migration/savevm.c          |   7 +-
 migration/trace-events      |   4 +
 migration/vmstate.c         | 188 +++++++++++++++++++++++++++++++++++---------
 target/alpha/machine.c      |   6 +-
 target/arm/machine.c        |  14 +++-
 target/i386/machine.c       |  26 ++++--
 target/mips/machine.c       |  14 +++-
 target/ppc/machine.c        |  12 ++-
 target/sparc/machine.c      |   6 +-
 tests/test-vmstate.c        | 147 ++++++++++++++++++++++++++++++++++
 25 files changed, 569 insertions(+), 106 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-01-05 16:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 16:32 Amit Shah [this message]
2017-01-05 16:32 ` [Qemu-devel] [PULL 1/4] migration: extend VMStateInfo Amit Shah
2017-01-05 16:32 ` [Qemu-devel] [PULL 2/4] migration: migrate QTAILQ Amit Shah
2017-01-05 16:32 ` [Qemu-devel] [PULL 3/4] tests/migration: Add test for QTAILQ migration Amit Shah
2017-01-05 16:32 ` [Qemu-devel] [PULL 4/4] migration: add error_report Amit Shah
2017-01-06 12:10 ` [Qemu-devel] [PULL 0/4] migration: QTAILQ migration Peter Maydell
2017-01-13  3:37   ` Amit Shah
2017-01-13  9:43     ` Peter Maydell
2017-01-16 18:22       ` 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=1483633930-7103-1-git-send-email-amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=duanj@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --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).