qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] virtio: migration fixes for memory region cache
Date: Fri, 24 Feb 2017 15:24:38 +0100	[thread overview]
Message-ID: <3455495c-2375-0327-a46d-3eeaa1e1aad6@redhat.com> (raw)
In-Reply-To: <20170222163734.13104-1-stefanha@redhat.com>

Hi Stephan,

On 22/02/2017 17:37, Stefan Hajnoczi wrote:
> v2:
>  * Avoid early region cache initialization in virtio_load() with wrong ring
>    addresses for VIRTIO-1 in Patch 2 [Cornelia]
> 
> Bug fixes for the recently added memory region cache in virtio.  This series
> fixes live migration, see patches for details.
> 
> Stefan Hajnoczi (2):
>   virtio: invalidate memory in vring_set_avail_event()
>   virtio: add missing region cache init in virtio_load()
> 
>  hw/virtio/virtio.c | 26 ++++++++++++++++++++------
>  1 file changed, 20 insertions(+), 6 deletions(-)
> 

For me this fixes virtio-net migration issue caused by "virtio: use
VRingMemoryRegionCaches for avail and used rings".

Tested-by: Eric Auger <eric.auger@redhat.com>

Thanks

Eric

  parent reply	other threads:[~2017-02-24 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 16:37 [Qemu-devel] [PATCH v2 0/2] virtio: migration fixes for memory region cache Stefan Hajnoczi
2017-02-22 16:37 ` [Qemu-devel] [PATCH v2 1/2] virtio: invalidate memory in vring_set_avail_event() Stefan Hajnoczi
2017-02-22 16:37 ` [Qemu-devel] [PATCH v2 2/2] virtio: add missing region cache init in virtio_load() Stefan Hajnoczi
2017-02-27 14:06   ` Cornelia Huck
2017-02-24 14:24 ` Auger Eric [this message]
2017-02-28 13:18 ` [Qemu-devel] [PATCH v2 0/2] virtio: migration fixes for memory region cache Stefan Hajnoczi

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=3455495c-2375-0327-a46d-3eeaa1e1aad6@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).