From: Juan Quintela <quintela@redhat.com>
To: Hyman Huang <yong.huang@smartx.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Leonardo Bras <leobras@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [v3 3/6] tests: Add migration dirty-limit capability test
Date: Thu, 02 Nov 2023 11:31:14 +0100 [thread overview]
Message-ID: <87pm0s30r1.fsf@secure.mitica> (raw)
In-Reply-To: <e55a302df9da7dbc00ad825f47f57c1a756d303e.1698847223.git.yong.huang@smartx.com> (Hyman Huang's message of "Wed, 1 Nov 2023 22:04:06 +0800")
Hyman Huang <yong.huang@smartx.com> wrote:
> 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.
>
> Note that this test case involves many passes, so it runs
> in slow mode only.
>
> Signed-off-by: Hyman Huang <yong.huang@smartx.com>
> Acked-by: Peter Xu <peterx@redhat.com>
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
> Message-Id: <a05e931ed147696bd5924e0582db67a734547a3f.1697815117.git.yong.huang@smartx.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2023-11-02 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:04 [v3 0/6] dirtylimit: miscellaneous patches Hyman Huang
2023-11-01 14:04 ` [v3 1/6] system/dirtylimit: Fix a race situation Hyman Huang
2023-11-02 10:28 ` Juan Quintela
2023-11-01 14:04 ` [v3 2/6] system/dirtylimit: Drop the reduplicative check Hyman Huang
2023-11-02 10:28 ` Juan Quintela
2023-11-01 14:04 ` [v3 3/6] tests: Add migration dirty-limit capability test Hyman Huang
2023-11-02 10:31 ` Juan Quintela [this message]
2023-11-01 14:04 ` [v3 4/6] tests/migration: Introduce dirty-ring-size option into guestperf Hyman Huang
2023-11-01 14:04 ` [v3 5/6] tests/migration: Introduce dirty-limit " Hyman Huang
2023-11-01 14:04 ` [v3 6/6] docs/migration: Add the dirty limit section Hyman Huang
2023-11-02 10:37 ` Juan Quintela
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=87pm0s30r1.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.