qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jianjun Duan <duanj@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, dmitry@daynix.com,
	peter.maydell@linaro.org, kraxel@redhat.com, mst@redhat.com,
	david@gibson.dropbear.id.au, pbonzini@redhat.com,
	veroniabahaa@gmail.com, quintela@redhat.com,
	amit.shah@redhat.com, mreitz@redhat.com, kwolf@redhat.com,
	rth@twiddle.net, aurelien@aurel32.net, leon.alrae@imgtec.com,
	blauwirbel@gmail.com, mark.cave-ayland@ilande.co.uk,
	mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [QEMU PATCH v17 0/4] migration: migrate QTAILQ
Date: Tue, 24 Jan 2017 11:40:30 +0000	[thread overview]
Message-ID: <20170124114030.GB20224@work-vm> (raw)
In-Reply-To: <1484852453-12728-1-git-send-email-duanj@linux.vnet.ibm.com>

* Jianjun Duan (duanj@linux.vnet.ibm.com) wrote:
> Hi all,

Queued.

Dave

>     Comments are welcome.     
> 
> v17: - Fixed a type cast issue in test-vmstate.c.
> Previous versions are:
> 
> v16: - Moved a variable to global in test-vmstate.c following Dave's suggestion.
> (link: http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg01187.html)
> 
> v15: - Improved error messages.
> (link: http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg01059.html)
> 
> v14: - Fixed a return statement.
> (link: http://lists.nongnu.org/archive/html/qemu-devel/2016-11/msg04467.html)
> 
> v13: - Changed some QTAILQ related macro names to match existing ones. 
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-11/msg00226.html)
> 
> v12: - Fixed type for put_qtailq which caused build break.
> (link: http://lists.gnu.org/archive/html/qemu-devel/2016-11/msg01328.html
> 
> v11: - Split error_report statements into a separate patch.
>      - Changed the signature of put. It now returns int type.
>      - Minor changes to QTAILQ macros. 
>          
> v10: - Fixed a typo.
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-10/msg01206.html)
> 
> v9: - No more hard encoding of QTAILQ layout information
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-10/msg01042.html)
> 
> v8: - Fixed a style issue. 
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-10/msg00874.html)
> 
> v7: - Fixed merge errors.
>     - Simplified macro definitions related to pointer arithmetic based QTAILQ access.
>     - Added test case for QTAILQ migration in tests/test-vmstate.c.
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-10/msg00711.html)
> 
> 
> v6: - Split from Power specific patches. 
>     - Dropped VMS_LINKED flag.
>     - Rebased to master.
>     - Added comments to clarify about put/get in VMStateInfo.  
> (link: http://lists.nongnu.org/archive/html/qemu-ppc/2016-10/msg00336.html)
> 
> v5: - Rebased to David's ppc-for-2.8. 
> (link: https://lists.nongnu.org/archive/html/qemu-devel/2016-10/msg00270.html)
> 
> v4: - Introduce a way to set customized instance_id in SaveStateEntry. Use it
>       to set instance_id for DRC using its unique index to address David 
>       Gibson's concern.
>     - Rename VMS_CSTM to VMS_LINKED based on Paolo Bonzini's suggestions.
>     - Clean up qjson stuff in put_qtailq. 
>     - Add trace for put_qtailq and get_qtailq based on David Gilbert's 
>       suggestion.
>     - Based on David's ppc-for-2.7. 
> (link: https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg07720.html)
> 
> v3: - Simplify overall design followng discussion with Paolo. No longer need
>       metadata to migrate QTAILQ.
>     - Extend VMStateInfo instead of adding similar fields to VMStateField.
>     - Clean up macros in qemu/queue.h.
> (link: https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg05695.html)
> 
> v2: - Introduce a general approach to migrate QTAILQ in qemu/queue.h.
>     - Migrate signalled field in the DRC state.
>     - Put the newly added migrating fields in subsections so that backward 
>       migration is not broken.  
>     - Set detach_cb field right after migration so that a migrated hot-unplug
>       event could finish its course.
> (link: https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg04188.html)
> 
> v1: - Inital version.
> (link: https://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg02601.html)
> 
> To make guest device (PCI, CPU and memory) hotplug work together 
> with guest migration, spapr drc state needs be transmitted in
> migration. This patch defines the VMStateDescription struct for
> spapr drc state to enable it.
> 
> To fix the potential racing between hotplug events on guest and 
> guest migration, ccs_list and pending_events of spapr state need be 
> transmitted in migration. This patch also takes care of it.
> 
> 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(-)
> 
> -- 
> 1.9.1
> 
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

      parent reply	other threads:[~2017-01-24 11:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 19:00 [Qemu-devel] [QEMU PATCH v17 0/4] migration: migrate QTAILQ Jianjun Duan
2017-01-19 19:00 ` [Qemu-devel] [QEMU PATCH v17 1/4] migration: extend VMStateInfo Jianjun Duan
2017-01-19 19:00 ` [Qemu-devel] [QEMU PATCH v17 2/4] migration: migrate QTAILQ Jianjun Duan
2017-01-19 19:00 ` [Qemu-devel] [QEMU PATCH v17 3/4] tests/migration: Add test for QTAILQ migration Jianjun Duan
2017-01-24 11:03   ` Dr. David Alan Gilbert
2017-01-19 19:00 ` [Qemu-devel] [QEMU PATCH v17 4/4] migration: add error_report Jianjun Duan
2017-01-24 11:40 ` Dr. David Alan Gilbert [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=20170124114030.GB20224@work-vm \
    --to=dgilbert@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dmitry@daynix.com \
    --cc=duanj@linux.vnet.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=leon.alrae@imgtec.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rth@twiddle.net \
    --cc=veroniabahaa@gmail.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).