[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v21 8/9] migration-test: Export migration-test util funtions
From: |
Peter Xu |
Subject: |
Re: [PATCH v21 8/9] migration-test: Export migration-test util funtions |
Date: |
Tue, 29 Mar 2022 14:54:27 -0400 |
On Wed, Mar 16, 2022 at 09:07:20PM +0800, huangy81@chinatelecom.cn wrote:
> +void wait_for_serial(const char *tmpfs, const char *side)
Passing over tmpfs over and over (even if it's mostly a constant) doesn't
sound appealing to me..
I hope there's still a way that we could avoid doing that when spliting the
file. Or, how about you just add a new test into migration-test? After
all all migration tests (including auto-converge) is there, and I don't
strongly feel that we need a separate file urgently.
Thanks,
--
Peter Xu
- [PATCH v21 0/9] support dirty restraint on vCPU, huangy81, 2022/03/16
- [PATCH v21 3/9] migration/dirtyrate: Refactor dirty page rate calculation, huangy81, 2022/03/16
- [PATCH v21 1/9] accel/kvm/kvm-all: Refactor per-vcpu dirty ring reaping, huangy81, 2022/03/16
- [PATCH v21 2/9] cpus: Introduce cpu_list_generation_id, huangy81, 2022/03/16
- [PATCH v21 4/9] softmmu/dirtylimit: Implement vCPU dirtyrate calculation periodically, huangy81, 2022/03/16
- [PATCH v21 5/9] accel/kvm/kvm-all: Introduce kvm_dirty_ring_size function, huangy81, 2022/03/16
- [PATCH v21 6/9] softmmu/dirtylimit: Implement virtual CPU throttle, huangy81, 2022/03/16
- [PATCH v21 7/9] softmmu/dirtylimit: Implement dirty page rate limit, huangy81, 2022/03/16
- [PATCH v21 8/9] migration-test: Export migration-test util funtions, huangy81, 2022/03/16
- Re: [PATCH v21 8/9] migration-test: Export migration-test util funtions,
Peter Xu <=
- [PATCH v21 9/9] tests: Add dirty page rate limit test, huangy81, 2022/03/16
- Re: [PATCH v21 0/9] support dirty restraint on vCPU, Hyman Huang, 2022/03/21