Re: [PATCH V2] KVM: selftests: Take large C-state exit latency into consideration

2024-04-16 Thread Chen, Zide
On 4/15/2024 4:23 PM, Sean Christopherson wrote: > On Fri, Apr 12, 2024, Zide Chen wrote: >> Currently, the migration worker delays 1-10 us, assuming that one >> KVM_RUN iteration only takes a few microseconds. But if C-state exit >> latencies are large enough, for example, hundreds or even

Re: [PATCH V2] KVM: selftests: Take large C-state exit latency into consideration

2024-04-15 Thread Sean Christopherson
On Fri, Apr 12, 2024, Zide Chen wrote: > Currently, the migration worker delays 1-10 us, assuming that one > KVM_RUN iteration only takes a few microseconds. But if C-state exit > latencies are large enough, for example, hundreds or even thousands > of microseconds on server CPUs, it may happen

[PATCH V2] KVM: selftests: Take large C-state exit latency into consideration

2024-04-12 Thread Zide Chen
Currently, the migration worker delays 1-10 us, assuming that one KVM_RUN iteration only takes a few microseconds. But if C-state exit latencies are large enough, for example, hundreds or even thousands of microseconds on server CPUs, it may happen that it's not able to bring the target CPU out