From: Juan Quintela <quintela@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Huth <thuth@redhat.com>, John Snow <jsnow@redhat.com>,
Li Zhijian <lizhijian@fujitsu.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Zhang Chen <chen.zhang@intel.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v2 2/6] tests/qtests: remove migration test iterations config
Date: Fri, 21 Apr 2023 23:54:55 +0200 [thread overview]
Message-ID: <87r0scgats.fsf@secure.mitica> (raw)
In-Reply-To: <20230421171411.566300-3-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Fri, 21 Apr 2023 18:14:07 +0100")
Daniel P. Berrangé <berrange@redhat.com> wrote:
> The 'unsigned int interations' config for migration is somewhat
> overkill. Most tests don't set it, and a value of '0' is treated
> as equivalent to '1'. The only test that does set it, xbzrle,
> used a value of '2'.
>
> This setting, however, only relates to the migration iterations
> that take place prior to allowing convergence. IOW, on top of
> this iteration count, there is always at least 1 further migration
> iteration done to deal with pages that are dirtied during the
> previous iteration(s).
>
> IOW, even with iterations==1, the xbzrle test will be running for
> a minimum of 2 iterations. With this in mind we can simplify the
> code and just get rid of the special case.
Perhaps the old code was already wrong, but we need at least three
iterations for the xbzrle test:
- 1st iteration: xbzrle is not used, nothing is on cache.
- 2nd iteration: pages are put into cache, no xbzrle is used because
there is no previous page.
- 3rd iteration: We really use xbzrle now against the copy of the
previous iterations.
And yes, this should be commented somewhere.
Later, Juan.
next prev parent reply other threads:[~2023-04-21 21:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 17:14 [PATCH v2 0/6] tests/qtest: make migration-test massively faster Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 1/6] tests/qtest: replace qmp_discard_response with qtest_qmp_assert_success Daniel P. Berrangé
2023-04-21 21:52 ` Juan Quintela
2023-04-23 2:22 ` Zhang, Chen
2023-04-21 17:14 ` [PATCH v2 2/6] tests/qtests: remove migration test iterations config Daniel P. Berrangé
2023-04-21 21:54 ` Juan Quintela [this message]
2023-04-26 9:07 ` Daniel P. Berrangé
2023-04-26 9:42 ` Juan Quintela
2023-04-26 10:15 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 3/6] tests/qtest: capture RESUME events during migration Daniel P. Berrangé
2023-04-21 21:59 ` Juan Quintela
2023-04-24 9:53 ` Daniel P. Berrangé
2023-05-26 11:56 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 4/6] tests/qtest: make more migration pre-copy scenarios run non-live Daniel P. Berrangé
2023-04-21 22:06 ` Juan Quintela
2023-04-24 21:01 ` Fabiano Rosas
2023-05-26 17:58 ` Daniel P. Berrangé
2023-05-31 12:15 ` Daniel P. Berrangé
2023-04-21 17:14 ` [PATCH v2 5/6] tests/qtest: massively speed up migration-tet Daniel P. Berrangé
2023-04-21 22:15 ` Juan Quintela
2023-04-21 17:14 ` [PATCH v2 6/6] tests/migration: Only run auto_converge in slow mode Daniel P. Berrangé
2023-04-23 2:41 ` Zhang, Chen
2023-04-24 5:58 ` Juan Quintela
2023-04-24 6:56 ` Thomas Huth
2023-04-24 8:05 ` Zhang, Chen
2023-04-24 8:06 ` Zhang, Chen
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=87r0scgats.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=chen.zhang@intel.com \
--cc=jsnow@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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).