qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: dgilbert@redhat.com, lvivier@redhat.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Check migration enabled features on both sides
Date: Tue, 13 Jun 2017 11:54:30 +0200	[thread overview]
Message-ID: <20170613095432.11623-1-quintela@redhat.com> (raw)

Hi

This was part of my multifd series, it just "requires" that
migartion features being enabled on both sides.
- XBZRLE: libvirt only enables it on source, so we don't test it

- compression threads: we check at reception when we receive a
                       compression page that we have compression
                       threads enabled.  Otherwise we exit with one
                       error.

- Now that we check if compression threads are enabled, we don't
  create the threads if they are not enabled.

  It makes debugging much easier, because I have less threads on
  destination to search where things are hang up.

Please review,

Thanks, Juan.

Juan Quintela (2):
  migration: Test for disabled features on reception
  migration: Don't create decompression threads if not enabled

 migration/ram.c | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)

-- 
2.9.4

             reply	other threads:[~2017-06-13  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  9:54 Juan Quintela [this message]
2017-06-13  9:54 ` [Qemu-devel] [PATCH 1/2] migration: Test for disabled features on reception Juan Quintela
2017-06-13 17:51   ` Dr. David Alan Gilbert
2017-06-14  8:45     ` Juan Quintela
2017-06-14  7:27   ` Peter Xu
2017-06-14  8:46     ` Juan Quintela
2017-06-13  9:54 ` [Qemu-devel] [PATCH 2/2] migration: Don't create decompression threads if not enabled Juan Quintela
2017-06-14  7:28   ` Peter Xu
2017-06-14  7:46     ` Juan Quintela
2017-06-14  7:50       ` Peter Xu

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=20170613095432.11623-1-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@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).