From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v1] tests/qtest/migration: Fix auto-converge test
Date: Tue, 12 May 2026 17:00:25 -0400 [thread overview]
Message-ID: <agOU6ZZ3k95TtCIG@x1.local> (raw)
In-Reply-To: <20260512141338.10089-1-farosas@suse.de>
On Tue, May 12, 2026 at 11:13:38AM -0300, Fabiano Rosas wrote:
> We fixed the cpu throttling sync thread affecting the
> dirty-sync-count, but the test still relies on it to gauge for
> progress. Remove that block from the test with no replacement.
>
> While here remove several incorrect or redundant comments.
>
> Fixes: 9519d3667a ("migration: Move iteration counter out of RAM")
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Oops, thanks for fixing this. Queued.
--
Peter Xu
prev parent reply other threads:[~2026-05-12 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 14:13 [PATCH v1] tests/qtest/migration: Fix auto-converge test Fabiano Rosas
2026-05-12 21:00 ` Peter Xu [this message]
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=agOU6ZZ3k95TtCIG@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@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