qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, quintela@redhat.com, amit.shah@redhat.com
Cc: aarcange@redhat.com, den@openvz.org, marcel.a@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/6] postcopy (& 1 test) patch for 2.7
Date: Tue, 17 May 2016 13:55:49 +0100	[thread overview]
Message-ID: <1463489755-30703-1-git-send-email-dgilbert@redhat.com> (raw)

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

Hi,
  This is a small set of postcopy changes, the largest of which
is an x86 test for postcopy.

Andrea's libqtest change came about from running my test under very heavy
load.

The test includes a self contained migration workload that rapidly changes
RAM in a predictable fashion allowing us to end up in postcopy mode and
also to be able to check the contents of RAM.

  Note this sometimes fails on Linux kernels 4.5 (and current 4.6) which
  have a KVM+THP bug. Use this fix:
     https://lists.gnu.org/archive/html/qemu-devel/2016-04/msg04028.html

v4:
  Add a patch to fail migrate-set-capability when turning on postcopy if we
  don't have the kernel support.

v3:
  Change all the test asserts to be g_assert macros (Marcel's suggestion)

v2:
  Split 'Add stats...' into two (Eric's comment)
  Test:
      Survive qmp events landing when we're expecting a response from the
      command (qmp/libqtest doesn't help in that)
      Fix a race where we'd start postcopy early

Dave

Andrea Arcangeli (1):
  tests: fix libqtest socket timeouts

Dr. David Alan Gilbert (5):
  Postcopy: Avoid 0 length discards
  Migration: Split out ram part of qmp_query_migrate
  Postcopy: Add stats on page requests
  test: Postcopy
  Postcopy: Check for support when setting the capability

 hmp.c                         |   4 +
 include/migration/migration.h |   2 +
 migration/migration.c         |  73 +++----
 migration/ram.c               |   5 +-
 qapi-schema.json              |   6 +-
 tests/Makefile                |   2 +
 tests/libqtest.c              |   2 +-
 tests/postcopy-test.c         | 455 ++++++++++++++++++++++++++++++++++++++++++
 8 files changed, 511 insertions(+), 38 deletions(-)
 create mode 100644 tests/postcopy-test.c

-- 
2.5.5

             reply	other threads:[~2016-05-17 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 12:55 Dr. David Alan Gilbert (git) [this message]
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 1/6] Postcopy: Avoid 0 length discards Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 2/6] Migration: Split out ram part of qmp_query_migrate Dr. David Alan Gilbert (git)
2016-05-23  7:02   ` Amit Shah
2016-05-31 16:10     ` Dr. David Alan Gilbert
2016-06-01  3:48       ` Amit Shah
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 3/6] Postcopy: Add stats on page requests Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 4/6] test: Postcopy Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 5/6] tests: fix libqtest socket timeouts Dr. David Alan Gilbert (git)
2016-05-17 12:55 ` [Qemu-devel] [PATCH v4 6/6] Postcopy: Check for support when setting the capability Dr. David Alan Gilbert (git)

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=1463489755-30703-1-git-send-email-dgilbert@redhat.com \
    --to=dgilbert@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=den@openvz.org \
    --cc=marcel.a@redhat.com \
    --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).