On Mon, Sep 9, 2024 at 10:03 PM Peter Maydell <peter.mayd...@linaro.org> wrote:
> On Mon, 9 Sept 2024 at 14:51, Hyman Huang <yong.hu...@smartx.com> wrote: > > > > Despite the fact that the responsive CPU throttle is enabled, > > the dirty sync count may not always increase because this is > > an optimization that might not happen in any situation. > > > > This test case just making sure it doesn't interfere with any > > current functionality. > > > > Signed-off-by: Hyman Huang <yong.hu...@smartx.com> > > tests/qtest/migration-test already runs 75 different > subtests, takes up a massive chunk of our "make check" > time, and is very commonly a "times out" test on some > of our CI jobs. It runs on five different guest CPU > architectures, each one of which takes between 2 and > 5 minutes to complete the full migration-test. > > Do we really need to make it even bigger? > No, I don't insist on that; the cpu-responsive-throttle parameter may also be enabled on the existing migrate_auto_converge test case by default. Thank for the comment. Yong. > > thanks > -- PMM > -- Best regards
