From: Peter Xu <peterx@redhat.com>
To: ~hyman <yong.huang@smartx.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH QEMU 1/3] tests: Add migration dirty-limit capability test
Date: Fri, 28 Jul 2023 15:45:13 -0400 [thread overview]
Message-ID: <ZMQayZ3f4g8PSKdf@x1n> (raw)
In-Reply-To: <169056463135.22823.13693920045521586976-1@git.sr.ht>
Yong,
On Thu, Jun 08, 2023 at 12:46:45AM +0800, ~hyman wrote:
> From: Hyman Huang(黄勇) <yong.huang@smartx.com>
>
> Add migration dirty-limit capability test if kernel support
> dirty ring.
>
> Migration dirty-limit capability introduce dirty limit
> capability, two parameters: x-vcpu-dirty-limit-period and
> vcpu-dirty-limit are introduced to implement the live
> migration with dirty limit.
>
> The test case does the following things:
> 1. start src, dst vm and enable dirty-limit capability
> 2. start migrate and set cancel it to check if dirty limit
> stop working.
> 3. restart dst vm
> 4. start migrate and enable dirty-limit capability
> 5. check if migration satisfy the convergence condition
> during pre-switchover phase.
>
> Signed-off-by: Hyman Huang(黄勇) <yong.huang@smartx.com>
How long does the test normally take? How stable is it (the duration, not
the test itself; I assume it should be robust or it'll be a bigger problem..)?
Daniel just reworked the tests to shrink all tests to run in around 1m40s
locally here on a decent x86. I hope this test won't take too long to
frustrate CI again.
--
Peter Xu
next prev parent reply other threads:[~2023-07-28 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:17 [PATCH QEMU 0/3] migration: enrich the dirty-limit test case ~hyman
2023-06-07 16:46 ` [PATCH QEMU 1/3] tests: Add migration dirty-limit capability test ~hyman
2023-07-28 19:45 ` Peter Xu [this message]
2023-07-26 18:25 ` [PATCH QEMU 2/3] tests/migration: Introduce dirty-ring-size option into guestperf ~hyman
2023-07-26 18:50 ` [PATCH QEMU 3/3] tests/migration: Introduce dirty-limit " ~hyman
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=ZMQayZ3f4g8PSKdf@x1n \
--to=peterx@redhat.com \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
--cc=yong.huang@smartx.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).